Activity trends and workouts

ABSTRACT

The present disclosure generally relates to computer user interfaces, and more specifically to techniques for presenting activity trends and managing workouts.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. non-Provisional applicationSer. No. 17/852,020, which is a Continuation of U.S. non-Provisionalapplication Ser. No. 16/994,352, entitled “ACTIVITY TRENDS ANDWORKOUTS,” filed on Aug. 14, 2020, which is a Continuation of U.S.non-Provisional application Ser. No. 16/588,950, entitled “ACTIVITYTRENDS AND WORKOUTS,” filed on Sep. 30, 2019, which claims priority toU.S. Provisional Patent Application Ser. No. 62/844,063, entitled“ACTIVITY TRENDS AND WORKOUTS,” filed on May 6, 2019, the contents ofeach of which are hereby incorporated by reference in their entirety.

FIELD

The present disclosure relates generally to computer user interfaces,and more specifically to techniques for presenting activity trends andmanaging workouts.

BACKGROUND

Users rely on portable multifunction devices for a variety ofoperations, including tracking activity. Such users may want to easilytrack the activity and view details related to the activity.

BRIEF SUMMARY

Some techniques for presenting activity trends and managing workoutsusing electronic devices, however, are generally cumbersome andinefficient. For example, some existing techniques use a complex andtime-consuming user interface, which may include multiple key presses orkeystrokes. Existing techniques require more time than necessary,wasting user time and device energy. This latter consideration isparticularly important in battery-operated devices.

Accordingly, the present technique provides electronic devices withfaster, more efficient methods and interfaces for presenting activitytrends and managing workouts. Such methods and interfaces optionallycomplement or replace other methods for presenting activity trends andmanaging workouts. Such methods and interfaces reduce the cognitiveburden on a user and produce a more efficient human-machine interface.For battery-operated computing devices, such methods and interfacesconserve power and increase the time between battery charges.

In some examples, a method is provided for execution at an electronicdevice including a display device. The method comprises receiving:activity data corresponding to a first activity metric for a first timeperiod, and activity data corresponding to the first activity metric fora second time period different from the first period of time. The methodfurther comprises receiving a request to display a first user interface.The method further comprises, in response to receiving the request,displaying, via the display device, the first user interface including:in accordance with a determination that a relationship between theactivity data corresponding to the first activity metric for the firsttime period and the activity data corresponding to the first activitymetric for the second time period is a first type, displaying arepresentation of the first activity metric in a first portion of thefirst user interface; and in accordance with a determination that therelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa second type, displaying the representation of the first activitymetric in a second portion of the first user interface different fromthe first portion.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions forperforming the method discussed above.

In some examples, an electronic device comprising. a display device; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors is provided. In someexamples, the one or more programs include instructions for performingthe method discussed above.

In some examples, an electronic device comprising: a display device andmeans for performing the method discussed above.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions for:receiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period different from the first period of time;receiving a request to display a first user interface; and in responseto receiving the request, displaying, via the display device, the firstuser interface including: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, displaying a representation of the first activity metricin a first portion of the first user interface: and in accordance with adetermination that the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a second type, displaying the representation ofthe first activity metric in a second portion of the first userinterface different from the first portion.

In some examples, a transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device with a display device is provided. In someexamples, the one or more programs include instructions for: receiving:activity data corresponding to a first activity metric for a first timeperiod; and activity data corresponding to the first activity metric fora second time period different from the first period of time; receivinga request to display a first user interface; and in response toreceiving the request, displaying, via the display device, the firstuser interface including: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, displaying a representation of the first activity metricin a first portion of the first user interface: and in accordance with adetermination that the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a second type, displaying the representation ofthe first activity metric in a second portion of the first userinterface different from the first portion.

In some examples, an electronic device, comprising: a display; one ormore processors; and memory storing one or more programs configured tobe executed by the one or more processors is provided. In some examples,the one or more programs include instructions for: receiving: activitydata corresponding to a first activity metric for a first time period;and activity data corresponding to the first activity metric for asecond time period different from the first period of time; receiving arequest to display a first user interface; and in response to receivingthe request, displaying, via the display device, the first userinterface including: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, displaying a representation of the first activity metricin a first portion of the first user interface: and in accordance with adetermination that the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a second type, displaying the representation ofthe first activity metric in a second portion of the first userinterface different from the first portion.

In some examples, an electronic device, comprising: a display isprovided. In some examples, the electronic device includes: means forreceiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period different from the first period of time;means for receiving a request to display a first user interface; and inresponse to receiving the request, means for displaying, via the displaydevice, the first user interface including: in accordance with adetermination that a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type, means for displaying arepresentation of the first activity metric in a first portion of thefirst user interface; and in accordance with a determination that therelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa second type, means for displaying the representation of the firstactivity metric in a second portion of the first user interfacedifferent from the first portion.

In some examples, a method performed method at an electronic deviceincluding a display device is provided. In some examples, the methodcomprises: receiving: activity data corresponding to a first activitymetric for a first time period; and activity data corresponding to thefirst activity metric for a second time period, wherein the first timeperiod is a subset of the second time period; receiving a request todisplay a first user interface; and in response to receiving therequest, displaying, via the display device, the first user interfaceincluding: representation of the activity data corresponding to thefirst activity metric for the first time period; a representation of theactivity data corresponding to the first activity metric for the secondtime period; and representation of a comparison of the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions forperforming the method described above.

In some examples, an electronic device comprising: a display device, oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors is provided. In someexamples, the one or more programs include instructions for performingthe method discussed above.

In some examples, an electronic device comprising: a display device andmeans for performing the method discussed above.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions for:receiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, wherein the first time period is asubset of the second time period; receiving a request to display a firstuser interface; and in response to receiving the request, displaying,via the display device, the first user interface including: arepresentation of the activity data corresponding to the first activitymetric for the first time period; a representation of the activity datacorresponding to the first activity metric for the second time period;and a representation of a comparison of the activity data correspondingto the first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod.

In some examples, a transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device with a display device is provided. In someexamples, the one or more programs include instructions for: receiving:activity data corresponding to a first activity metric for a first timeperiod; and activity data corresponding to the first activity metric fora second time period, wherein the first time period is a subset of thesecond time period; receiving a request to display a first userinterface; and in response to receiving the request, displaying, via thedisplay device, the first user interface including: a representation ofthe activity data corresponding to the first activity metric for thefirst time period; a representation of the activity data correspondingto the first activity metric for the second time period; and arepresentation of a comparison of the activity data corresponding to thefirst activity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period.

In some examples, an electronic device, comprising: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors is provided. Insome examples, the one or more programs include instructions for:receiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, wherein the first time period is asubset of the second time period; receiving a request to display a firstuser interface; and in response to receiving the request, displaying,via the display device, the first user interface including: arepresentation of the activity data corresponding to the first activitymetric for the first time period; a representation of the activity datacorresponding to the first activity metric for the second time period;and a representation of a comparison of the activity data correspondingto the first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod.

In some examples, an electronic device, comprising: a display device isprovided. In some examples, the electronic device includes: means forreceiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, wherein the first time period is asubset of the second time period; means for receiving a request todisplay a first user interface; and in response to receiving therequest, means for displaying, via the display device, the first userinterface including: a representation of the activity data correspondingto the first activity metric for the first time period; a representationof the activity data corresponding to the first activity metric for thesecond time period; and a representation of a comparison of the activitydata corresponding to the first activity metric for the first timeperiod and the activity data corresponding to the first activity metricfor the second time period.

In some examples, a method to be performed at an electronic deviceincluding a display device is provided. In some examples, the methodcomprises: receiving: activity data corresponding to a first activitymetric for a first time period; and activity data corresponding to thefirst activity metric for a second time period, different than the firstperiod of time; receiving a request to display a first user interface;and in response to receiving the request, displaying, via the displaydevice, the first user interface, the first user interface including arepresentation of the first activity metric, wherein the representationof the first activity metric includes: in accordance with adetermination that a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type, a first coaching indicationincluding a prediction corresponding to when the relationship willtransition from being of the first type to being of a second type,different from the first type, while maintaining a future level ofactivity for the first activity metric; and in accordance with adetermination that the relationship is a third type different from thefirst type, a second coaching indication that does not include aprediction corresponding to when the relationship will transition frombeing of the third type to being of the second type.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions forperforming the method described above.

In some examples, an electronic device comprising: a display device; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors is provided. In someexamples, the one or more programs include instructions for performingthe method discussed above.

In some examples, an electronic device comprising: a display device andmeans for performing the method discussed above.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions for:receiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, different than the first period oftime; receiving a request to display a first user interface; and inresponse to receiving the request, displaying, via the display device,the first user interface, the first user interface including arepresentation of the first activity metric, wherein the representationof the first activity metric includes: in accordance with adetermination that a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type, a first coaching indicationincluding a prediction corresponding to when the relationship willtransition from being of the first type to being of a second type,different from the first type, while maintaining a future level ofactivity for the first activity metric; and in accordance with adetermination that the relationship is a third type different from thefirst type, a second coaching indication that does not include aprediction corresponding to when the relationship will transition frombeing of the third type to being of the second type.

In some examples, a transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device with a display device is provided. In someexamples, the one or more programs include instructions for: receiving:activity data corresponding to a first activity metric for a first timeperiod; and activity data corresponding to the first activity metric fora second time period, different than the first period of time; receivinga request to display a first user interface; and in response toreceiving the request, displaying, via the display device, the firstuser interface, the first user interface including a representation ofthe first activity metric, wherein the representation of the firstactivity metric includes: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, a first coaching indication including a predictioncorresponding to when the relationship will transition from being of thefirst type to being of a second type, different from the first type,while maintaining a future level of activity for the first activitymetric; and in accordance with a determination that the relationship isa third type different from the first type, a second coaching indicationthat does not include a prediction corresponding to when therelationship will transition from being of the third type to being ofthe second type.

In some examples, an electronic device, comprising: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors is provided. Insome examples, the one or more programs include instructions for:receiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, different than the first period oftime; receiving a request to display a first user interface; and inresponse to receiving the request, displaying, via the display device,the first user interface, the first user interface including arepresentation of the first activity metric, wherein the representationof the first activity metric includes: in accordance with adetermination that a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type, a first coaching indicationincluding a prediction corresponding to when the relationship willtransition from being of the first type to being of a second type,different from the first type, while maintaining a future level ofactivity for the first activity metric; and in accordance with adetermination that the relationship is a third type different from thefirst type, a second coaching indication that does not include aprediction corresponding to when the relationship will transition frombeing of the third type to being of the second type.

In some examples, an electronic device, comprising a display device isprovided. In some examples, the electronic device includes: means forreceiving: activity data corresponding to a first activity metric for afirst time period; and activity data corresponding to the first activitymetric for a second time period, different than the first period oftime; means for receiving a request to display a first user interface;and in response to receiving the request, means for displaying, via thedisplay device, the first user interface, the first user interfaceincluding a representation of the first activity metric, wherein therepresentation of the first activity metric includes: in accordance witha determination that a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type, a first coaching indicationincluding a prediction corresponding to when the relationship willtransition from being of the first type to being of a second type,different from the first type, while maintaining a future level ofactivity for the first activity metric; and in accordance with adetermination that the relationship is a third type different from thefirst type, a second coaching indication that does not include aprediction corresponding to when the relationship will transition frombeing of the third type to being of the second type.

In some examples, a method performed at an electronic device including adisplay device is provided. The method comprises: displaying, via thedisplay device, a first instance of a first user interface including afirst set of affordances associated with physical activity trackingfunctions, wherein the first set of affordances includes a firstaffordance associated with a first physical activity tracking function;while displaying the first instance of the first user interface,receiving a user input; and in response to receiving the user input: inaccordance with a determination that the user input is detected at thefirst affordance in the first set of affordances, launching the firstphysical activity tracking function; and in accordance with adetermination that the user input is detected at a second affordance inthe first set of affordances, displaying a second user interface thatincludes a third affordance associated with a second physical activitytracking function; receiving a set of one or more inputs, the set of oneor more inputs including an input corresponding to selection of thethird affordance; and in response to receiving the set of one or moreinputs, displaying a second instance of first user interface, wherein:the second instance of the first user interface includes the firstaffordance and a fourth affordance associated with the second physicalactivity tracking function, and the first instance of the first userinterface does not include an affordance associated with the secondphysical activity tracking function.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided. Insome examples, the one or more programs include instructions forperforming the method described above.

In some examples, an electronic device comprising: a display device; oneor more processors; and memory storing one or more programs configuredto be executed by the one or more processors is provided. In someexamples, the one or more programs include instructions for performingthe method discussed above.

In some examples, an electronic device comprising: a display device andmeans for performing the method discussed above.

In some examples, a non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of an electronic device with a display device is provided.The one or more programs include instructions for: displaying, via thedisplay device, a first instance of a first user interface including afirst set of affordances associated with physical activity trackingfunctions, wherein the first set of affordances includes a firstaffordance associated with a first physical activity tracking function;while displaying the first instance of the first user interface,receiving a user input; and in response to receiving the user input: inaccordance with a determination that the user input is detected at thefirst affordance in the first set of affordances, launching the firstphysical activity tracking function; and in accordance with adetermination that the user input is detected at a second affordance inthe first set of affordances, displaying a second user interface thatincludes a third affordance associated with a second physical activitytracking function; receiving a set of one or more inputs, the set of oneor more inputs including an input corresponding to selection of thethird affordance; and in response to receiving the set of one or moreinputs, displaying a second instance of first user interface, wherein:the second instance of the first user interface includes the firstaffordance and a fourth affordance associated with the second physicalactivity tracking function, and the first instance of the first userinterface does not include an affordance associated with the secondphysical activity tracking function.

In some examples, a transitory computer-readable storage medium storingone or more programs configured to be executed by one or more processorsof an electronic device with a display device is provided. The one ormore programs include instructions for: displaying, via the displaydevice, a first instance of a first user interface including a first setof affordances associated with physical activity tracking functions,wherein the first set of affordances includes a first affordanceassociated with a first physical activity tracking function; whiledisplaying the first instance of the first user interface, receiving auser input; and in response to receiving the user input: in accordancewith a determination that the user input is detected at the firstaffordance in the first set of affordances, launching the first physicalactivity tracking function; and in accordance with a determination thatthe user input is detected at a second affordance in the first set ofaffordances, displaying a second user interface that includes a thirdaffordance associated with a second physical activity tracking function;receiving a set of one or more inputs, the set of one or more inputsincluding an input corresponding to selection of the third affordance;and in response to receiving the set of one or more inputs, displaying asecond instance of first user interface, wherein: the second instance ofthe first user interface includes the first affordance and a fourthaffordance associated with the second physical activity trackingfunction, and the first instance of the first user interface does notinclude an affordance associated with the second physical activitytracking function.

In some examples, an electronic device, comprising: a display device;one or more processors; and memory storing one or more programsconfigured to be executed by the one or more processors is provided. Theone or more programs include instructions for: displaying, via thedisplay device, a first instance of a first user interface including afirst set of affordances associated with physical activity trackingfunctions, wherein the first set of affordances includes a firstaffordance associated with a first physical activity tracking function;while displaying the first instance of the first user interface,receiving a user input; and in response to receiving the user input: inaccordance with a determination that the user input is detected at thefirst affordance in the first set of affordances, launching the firstphysical activity tracking function; and in accordance with adetermination that the user input is detected at a second affordance inthe first set of affordances, displaying a second user interface thatincludes a third affordance associated with a second physical activitytracking function; receiving a set of one or more inputs, the set of oneor more inputs including an input corresponding to selection of thethird affordance; and in response to receiving the set of one or moreinputs, displaying a second instance of first user interface, wherein;the second instance of the first user interface includes the firstaffordance and a fourth affordance associated with the second physicalactivity tracking function, and the first instance of the first userinterface does not include an affordance associated with the secondphysical activity tracking function.

In some examples, an electronic device, comprising a display device isprovided. The electronic device further comprises: means displaying, viathe display device, a first instance of a first user interface includinga first set of affordances associated with physical activity trackingfunctions, wherein the first set of affordances includes a firstaffordance associated with a first physical activity tracking function;while displaying the first instance of the first user interface, meansfor receiving a user input; and in response to receiving the user input:in accordance with a determination that the user input is detected atthe first affordance in the first set of affordances, means forlaunching the first physical activity tracking function; and inaccordance with a determination that the user input is detected at asecond affordance in the first set of affordances, means for displayinga second user interface that includes a third affordance associated witha second physical activity tracking function; means for receiving a setof one or more inputs, the set of one or more inputs including an inputcorresponding to selection of the third affordance; and in response toreceiving the set of one or more inputs, means for displaying a secondinstance of first user interface, wherein: the second instance of thefirst user interface includes the first affordance and a fourthaffordance associated with the second physical activity trackingfunction, and the first instance of the first user interface does notinclude an affordance associated with the second physical activitytracking function.

Executable instructions for performing these functions are, optionally,included in a non-transitory computer-readable storage medium or othercomputer program product configured for execution by one or moreprocessors. Executable instructions for performing these functions are,optionally, included in a transitory computer-readable storage medium orother computer program product configured for execution by one or moreprocessors.

Thus, devices are provided with faster, more efficient methods andinterfaces for presenting activity trends and managing workouts, therebyincreasing the effectiveness, efficiency, and user satisfaction withsuch devices. Such methods and interfaces can complement or replaceother methods for presenting activity trends and managing workouts.

DESCRIPTION OF THE FIGURES

For a better understanding of the various described embodiments,reference should be made to the Description of Embodiments below, inconjunction with the following drawings in which like reference numeralsrefer to corresponding parts throughout the figures.

FIG. 1A is a block diagram illustrating a portable multifunction devicewith a touch-sensitive display in accordance with some embodiments.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments.

FIG. 2 illustrates a portable multifunction device having a touch screenin accordance with some embodiments.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on a portable multifunction device in accordance with someembodiments.

FIG. 4B illustrates an exemplary user interface for a multifunctiondevice with a touch-sensitive surface that is separate from the displayin accordance with some embodiments.

FIG. 5A illustrates a personal electronic device in accordance with someembodiments.

FIG. 5B is a block diagram illustrating a personal electronic device inaccordance with some embodiments.

FIG. 6A depicts an electronic device displaying a home user interfacevia a display device.

FIG. 6B depicts an electronic device displaying an information userinterface for an activity application.

FIG. 6C depicts an electronic device displaying an instance of a 90-daytrends user interface via a display device when an insufficient amountof data to identify a trend has been received for multiple activitymetrics.

FIG. 6D depicts an electronic device displaying an instance of a 90-daytrends user interface via a display device when all activity metricshave a negative trend within the last 90 days as compared to the last365 days.

FIG. 6E depicts an electronic device displaying an instance of a 90-daytrends user interface via a display device when some activity metricshave a positive trend and other activity metrics have a negative trendwithin the last 90 days as compared to the last 365 days.

FIG. 6F depicts an electronic device displaying an instance of a 90-daytrends user interface via a display device when all activity metricshave a positive trend within the last 90 days as compared to the last365 days.

FIG. 6G depicts an electronic device displaying a detailed exercise userinterface.

FIG. 6H depicts an electronic device displaying a ready-to-user userinterface via a display device when activity trends are ready to beviewed on a second device.

FIG. 6I depicts an electronic device displaying a mid-month-update userinterface via a display device when activity trends are available to beviewed on a second device.

FIGS. 7A-7B are a flow diagram illustrating a method for presentingactivity trends using an electronic device in accordance with someembodiments.

FIGS. 8A-8B are a flow diagram illustrating a method for presentingactivity trends using an electronic device in accordance with someembodiments.

FIG. 9 is a flow diagram illustrating a method for presenting activitytrends using an electronic device in accordance with some embodiments.

FIG. 10A depicts an electronic device displaying a watch face userinterface via a display device.

FIG. 10B depicts an electronic device displaying a workout platter userinterface via a display device.

FIG. 10C depicts an electronic device displaying a walk user interfacevia a display device.

FIG. 10D depicts an electronic device displaying a control userinterface via a display device.

FIG. 10E depicts an electronic device displaying a workout platter userinterface via a display device 1002 and performing a scrollingoperation.

FIG. 10F depicts an electronic device receiving user input correspondingto selection of a more workouts affordance.

FIG. 10G depicts an electronic device displaying a workout list userinterface via a display device.

FIG. 10H depicts an electronic device receiving user input correspondingto selection of an AUS football affordance.

FIG. 101 depicts an electronic device displaying a workout platter userinterface via a display device.

FIG. 10J depicts an electronic device displaying an AUS footballinterface via a display device 1002.

FIG. 10K depicts an electronic device displaying a control userinterface via a display device.

FIG. 10L depicts an electronic device displaying a workout platter userinterface via a display device.

FIG. 10M depicts an electronic device displaying a workout platter userinterface via a display device with an AUS football affordance moved tothe left and a delete affordance displayed in a location that was atleast partially covered up by the AUS football affordance prior to beingmoved to the left.

FIG. 10N depicts an electronic device displaying a workout platter userinterface via a display device without an AUS football affordance.

FIGS. 11A-11B are a flow diagram illustrating methods of organizingworkouts in accordance with some embodiments.

FIG. 12A depicts an electronic device displaying an activity applicationuser interface via a display device 1002.

FIG. 12B depicts an electronic device displaying an activity userinterface via a display device.

FIG. 12C depicts an electronic device displaying a friends userinterface via a display device.

FIG. 12D depicts an electronic device displaying an awards userinterface via a display device.

FIG. 12E depicts an electronic device displaying a non-awarded detaileduser interface via a display device.

FIG. 12F depicts an electronic device displaying an awarded detaileduser interface via a display device.

DESCRIPTION OF EMBODIMENTS

The following description sets forth exemplary methods, parameters, andthe like. It should be recognized, however, that such description is notintended as a limitation on the scope of the present disclosure but isinstead provided as a description of exemplary embodiments.

There is a need for electronic devices that provide efficient methodsand interfaces for presenting activity trends and managing workouts.Below, FIGS. 1A-1B, 2, 3, 4A-4B, and 5A-5B provide a description ofexemplary devices for performing the techniques for managing eventnotifications. FIGS. 6A-6I illustrate exemplary user interfaces forpresenting activity trends. The user interfaces in FIGS. 6A-6I are usedto illustrate the processes described below, including the processes inFIGS. 7A-7B, 8A-8B, and 9 . FIGS. 7A-7B are a flow diagram illustratingmethods of presenting activity trends in accordance with someembodiments. FIGS. 8A-8B are a flow diagram illustrating methods ofpresenting activity trends in accordance with some embodiments. FIG. 9is a flow diagram illustrating methods of presenting activity trends inaccordance with some embodiments. FIGS. 10A-10N illustrate exemplaryuser interfaces for managing workouts. The user interfaces in FIGS.10A-10N are used to illustrate the processes described below, includingthe processes in FIGS. 11A-11B. FIGS. 1A-11B are a flow diagramillustrating methods of organizing workouts in accordance with someembodiments. FIGS. 12A-12F illustrate exemplary user interfaces fordisplaying awards.

Although the following description uses terms “first,” “second,” etc. todescribe various elements, these elements should not be limited by theterms. These terms are only used to distinguish one element fromanother. For example, a first touch could be termed a second touch, and,similarly, a second touch could be termed a first touch, withoutdeparting from the scope of the various described embodiments. The firsttouch and the second touch are both touches, but they are not the sametouch.

The terminology used in the description of the various describedembodiments herein is for the purpose of describing particularembodiments only and is not intended to be limiting. As used in thedescription of the various described embodiments and the appendedclaims, the singular forms “a,” “an,” and “the” are intended to includethe plural forms as well, unless the context clearly indicatesotherwise. It will also be understood that the term “and/or” as usedherein refers to and encompasses any and all possible combinations ofone or more of the associated listed items. It will be furtherunderstood that the terms “includes,” “including,” “comprises,” and/or“comprising,” when used in this specification, specify the presence ofstated features, integers, steps, operations, elements, and/orcomponents, but do not preclude the presence or addition of one or moreother features, integers, steps, operations, elements, components,and/or groups thereof.

The term “if” is, optionally, construed to mean “when” or “upon” or “inresponse to determining” or “in response to detecting,” depending on thecontext. Similarly, the phrase “if it is determined” or “if [a statedcondition or event] is detected” is, optionally, construed to mean “upondetermining” or “in response to determining” or “upon detecting [thestated condition or event]” or “in response to detecting [the statedcondition or event],” depending on the context.

Embodiments of electronic devices, user interfaces for such devices, andassociated processes for using such devices are described. In someembodiments, the device is a portable communications device, such as amobile telephone, that also contains other functions, such as PDA and/ormusic player functions. Exemplary embodiments of portable multifunctiondevices include, without limitation, the iPhone®, iPod Touch®, and iPad®devices from Apple Inc. of Cupertino, Calif. Other portable electronicdevices, such as laptops or tablet computers with touch-sensitivesurfaces (e.g., touch screen displays and/or touchpads), are,optionally, used. It should also be understood that, in someembodiments, the device is not a portable communications device, but isa desktop computer with a touch-sensitive surface (e.g., a touch screendisplay and/or a touchpad).

In the discussion that follows, an electronic device that includes adisplay and a touch-sensitive surface is described. It should beunderstood, however, that the electronic device optionally includes oneor more other physical user-interface devices, such as a physicalkeyboard, a mouse, and/or a joystick.

The device typically supports a variety of applications, such as one ormore of the following: a drawing application, a presentationapplication, a word processing application, a website creationapplication, a disk authoring application, a spreadsheet application, agaming application, a telephone application, a video conferencingapplication, an e-mail application, an instant messaging application, aworkout support application, a photo management application, a digitalcamera application, a digital video camera application, a web browsingapplication, a digital music player application, and/or a digital videoplayer application.

The various applications that are executed on the device optionally useat least one common physical user-interface device, such as thetouch-sensitive surface. One or more functions of the touch-sensitivesurface as well as corresponding information displayed on the deviceare, optionally, adjusted and/or varied from one application to the nextand/or within a respective application. In this way, a common physicalarchitecture (such as the touch-sensitive surface) of the deviceoptionally supports the variety of applications with user interfacesthat are intuitive and transparent to the user.

Attention is now directed toward embodiments of portable devices withtouch-sensitive displays. FIG. 1A is a block diagram illustratingportable multifunction device 100 with touch-sensitive display system112 in accordance with some embodiments. Touch-sensitive display 112 issometimes called a “touch screen” for convenience and is sometimes knownas or called a “touch-sensitive display system.” Device 100 includesmemory 102 (which optionally includes one or more computer-readablestorage mediums), memory controller 122, one or more processing units(CPUs) 120, peripherals interface 118, RF circuitry 108, audio circuitry110, speaker 111, microphone 113, input/output (I/O) subsystem 106,other input control devices 116, and external port 124. Device 100optionally includes one or more optical sensors 164. Device 100optionally includes one or more contact intensity sensors 165 fordetecting intensity of contacts on device 100 (e.g., a touch-sensitivesurface such as touch-sensitive display system 112 of device 100).Device 100 optionally includes one or more tactile output generators 167for generating tactile outputs on device 100 (e.g., generating tactileoutputs on a touch-sensitive surface such as touch-sensitive displaysystem 112 of device 100 or touchpad 355 of device 300). Thesecomponents optionally communicate over one or more communication busesor signal lines 103.

As used in the specification and claims, the term “intensity” of acontact on a touch-sensitive surface refers to the force or pressure(force per unit area) of a contact (e.g., a finger contact) on thetouch-sensitive surface, or to a substitute (proxy) for the force orpressure of a contact on the touch-sensitive surface. The intensity of acontact has a range of values that includes at least four distinctvalues and more typically includes hundreds of distinct values (e.g., atleast 256). Intensity of a contact is, optionally, determined (ormeasured) using various approaches and various sensors or combinationsof sensors. For example, one or more force sensors underneath oradjacent to the touch-sensitive surface are, optionally, used to measureforce at various points on the touch-sensitive surface. In someimplementations, force measurements from multiple force sensors arecombined (e.g., a weighted average) to determine an estimated force of acontact. Similarly, a pressure-sensitive tip of a stylus is, optionally,used to determine a pressure of the stylus on the touch-sensitivesurface. Alternatively, the size of the contact area detected on thetouch-sensitive surface and/or changes thereto, the capacitance of thetouch-sensitive surface proximate to the contact and/or changes thereto,and/or the resistance of the touch-sensitive surface proximate to thecontact and/or changes thereto are, optionally, used as a substitute forthe force or pressure of the contact on the touch-sensitive surface. Insome implementations, the substitute measurements for contact force orpressure are used directly to determine whether an intensity thresholdhas been exceeded (e.g., the intensity threshold is described in unitscorresponding to the substitute measurements). In some implementations,the substitute measurements for contact force or pressure are convertedto an estimated force or pressure, and the estimated force or pressureis used to determine whether an intensity threshold has been exceeded(e.g., the intensity threshold is a pressure threshold measured in unitsof pressure). Using the intensity of a contact as an attribute of a userinput allows for user access to additional device functionality that mayotherwise not be accessible by the user on a reduced-size device withlimited real estate for displaying affordances (e.g., on atouch-sensitive display) and/or receiving user input (e.g., via atouch-sensitive display, a touch-sensitive surface, or aphysical/mechanical control such as a knob or a button).

As used in the specification and claims, the term “tactile output”refers to physical displacement of a device relative to a previousposition of the device, physical displacement of a component (e.g., atouch-sensitive surface) of a device relative to another component(e.g., housing) of the device, or displacement of the component relativeto a center of mass of the device that will be detected by a user withthe user's sense of touch. For example, in situations where the deviceor the component of the device is in contact with a surface of a userthat is sensitive to touch (e.g., a finger, palm, or other part of auser's hand), the tactile output generated by the physical displacementwill be interpreted by the user as a tactile sensation corresponding toa perceived change in physical characteristics of the device or thecomponent of the device. For example, movement of a touch-sensitivesurface (e.g., a touch-sensitive display or trackpad) is, optionally,interpreted by the user as a “down click” or “up click” of a physicalactuator button. In some cases, a user will feel a tactile sensationsuch as an “down click” or “up click” even when there is no movement ofa physical actuator button associated with the touch-sensitive surfacethat is physically pressed (e.g., displaced) by the user's movements. Asanother example, movement of the touch-sensitive surface is, optionally,interpreted or sensed by the user as “roughness” of the touch-sensitivesurface, even when there is no change in smoothness of thetouch-sensitive surface. While such interpretations of touch by a userwill be subject to the individualized sensory perceptions of the user,there are many sensory perceptions of touch that are common to a largemajority of users. Thus, when a tactile output is described ascorresponding to a particular sensory perception of a user (e.g., an “upclick,” a “down click,” “roughness”), unless otherwise stated, thegenerated tactile output corresponds to physical displacement of thedevice or a component thereof that will generate the described sensoryperception for a typical (or average) user.

It should be appreciated that device 100 is only one example of aportable multifunction device, and that device 100 optionally has moreor fewer components than shown, optionally combines two or morecomponents, or optionally has a different configuration or arrangementof the components. The various components shown in FIG. 1A areimplemented in hardware, software, or a combination of both hardware andsoftware, including one or more signal processing and/orapplication-specific integrated circuits.

Memory 102 optionally includes high-speed random access memory andoptionally also includes non-volatile memory, such as one or moremagnetic disk storage devices, flash memory devices, or othernon-volatile solid-state memory devices. Memory controller 122optionally controls access to memory 102 by other components of device100.

Peripherals interface 118 can be used to couple input and outputperipherals of the device to CPU 120 and memory 102. The one or moreprocessors 120 run or execute various software programs and/or sets ofinstructions stored in memory 102 to perform various functions fordevice 100 and to process data. In some embodiments, peripheralsinterface 118, CPU 120, and memory controller 122 are, optionally,implemented on a single chip, such as chip 104. In some otherembodiments, they are, optionally, implemented on separate chips.

RF (radio frequency) circuitry 108 receives and sends RF signals, alsocalled electromagnetic signals. RF circuitry 108 converts electricalsignals to/from electromagnetic signals and communicates withcommunications networks and other communications devices via theelectromagnetic signals. RF circuitry 108 optionally includes well-knowncircuitry for performing these functions, including but not limited toan antenna system, an RF transceiver, one or more amplifiers, a tuner,one or more oscillators, a digital signal processor, a CODEC chipset, asubscriber identity module (SIM) card, memory, and so forth. RFcircuitry 108 optionally communicates with networks, such as theInternet, also referred to as the World Wide Web (WWW), an intranetand/or a wireless network, such as a cellular telephone network, awireless local area network (LAN) and/or a metropolitan area network(MAN), and other devices by wireless communication. The RF circuitry 108optionally includes well-known circuitry for detecting near fieldcommunication (NFC) fields, such as by a short-range communicationradio. The wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), high-speed downlink packet access (HSDPA),high-speed uplink packet access (HSUPA), Evolution, Data-Only (EV-DO),HSPA, HSPA+, Dual-Cell HSPA (DC-HSPDA), long term evolution (LTE), nearfield communication (NFC), wideband code division multiple access(W-CDMA), code division multiple access (CDMA), time division multipleaccess (TDMA), Bluetooth, Bluetooth Low Energy (BTLE), Wireless Fidelity(Wi-Fi) (e.g., IEEE 802.11a, IEEE 802.11b, IEEE 802.11g, IEEE 802.11 n,and/or IEEE 802.1 lac), voice over Internet Protocol (VoIP), Wi-MAX, aprotocol for e-mail (e.g., Internet message access protocol (IMAP)and/or post office protocol (POP)), instant messaging (e.g., extensiblemessaging and presence protocol (XMPP), Session Initiation Protocol forInstant Messaging and Presence Leveraging Extensions (SIMPLE), InstantMessaging and Presence Service (IMPS)), and/or Short Message Service(SMS), or any other suitable communication protocol, includingcommunication protocols not yet developed as of the filing date of thisdocument.

Audio circuitry 110, speaker 111, and microphone 113 provide an audiointerface between a user and device 100. Audio circuitry 110 receivesaudio data from peripherals interface 118, converts the audio data to anelectrical signal, and transmits the electrical signal to speaker 111.Speaker 111 converts the electrical signal to human-audible sound waves.Audio circuitry 110 also receives electrical signals converted bymicrophone 113 from sound waves. Audio circuitry 110 converts theelectrical signal to audio data and transmits the audio data toperipherals interface 118 for processing. Audio data is, optionally,retrieved from and/or transmitted to memory 102 and/or RF circuitry 108by peripherals interface 118. In some embodiments, audio circuitry 110also includes a headset jack (e.g., 212, FIG. 2 ). The headset jackprovides an interface between audio circuitry 110 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (e.g., a headphone for one or both ears) and input(e.g., a microphone).

I/O subsystem 106 couples input/output peripherals on device 100, suchas touch screen 112 and other input control devices 116, to peripheralsinterface 118. I/O subsystem 106 optionally includes display controller156, optical sensor controller 158, depth camera controller 169,intensity sensor controller 159, haptic feedback controller 161, and oneor more input controllers 160 for other input or control devices. Theone or more input controllers 160 receive/send electrical signalsfrom/to other input control devices 116. The other input control devices116 optionally include physical buttons (e.g., push buttons, rockerbuttons, etc.), dials, slider switches, joysticks, click wheels, and soforth. In some alternate embodiments, input controller(s) 160 are,optionally, coupled to any (or none) of the following: a keyboard, aninfrared port, a USB port, and a pointer device such as a mouse. The oneor more buttons (e.g., 208, FIG. 2 ) optionally include an up/downbutton for volume control of speaker 111 and/or microphone 113. The oneor more buttons optionally include a push button (e.g., 206, FIG. 2 ).

A quick press of the push button optionally disengages a lock of touchscreen 112 or optionally begins a process that uses gestures on thetouch screen to unlock the device, as described in U.S. patentapplication Ser. No. 11/322,549, “Unlocking a Device by PerformingGestures on an Unlock Image,” filed Dec. 23, 2005, U.S. Pat. No.7,657,849, which is hereby incorporated by reference in its entirety. Alonger press of the push button (e.g., 206) optionally turns power todevice 100 on or off. The functionality of one or more of the buttonsare, optionally, user-customizable. Touch screen 112 is used toimplement virtual or soft buttons and one or more soft keyboards.

Touch-sensitive display 112 provides an input interface and an outputinterface between the device and a user. Display controller 156 receivesand/or sends electrical signals from/to touch screen 112. Touch screen112 displays visual output to the user. The visual output optionallyincludes graphics, text, icons, video, and any combination thereof(collectively termed “graphics”). In some embodiments, some or all ofthe visual output optionally corresponds to user-interface objects.

Touch screen 112 has a touch-sensitive surface, sensor, or set ofsensors that accepts input from the user based on haptic and/or tactilecontact. Touch screen 112 and display controller 156 (along with anyassociated modules and/or sets of instructions in memory 102) detectcontact (and any movement or breaking of the contact) on touch screen112 and convert the detected contact into interaction withuser-interface objects (e.g., one or more soft keys, icons, web pages,or images) that are displayed on touch screen 112. In an exemplaryembodiment, a point of contact between touch screen 112 and the usercorresponds to a finger of the user.

Touch screen 112 optionally uses LCD (liquid crystal display)technology, LPD (light emitting polymer display) technology, or LED(light emitting diode) technology, although other display technologiesare used in other embodiments. Touch screen 112 and display controller156 optionally detect contact and any movement or breaking thereof usingany of a plurality of touch sensing technologies now known or laterdeveloped, including but not limited to capacitive, resistive, infrared,and surface acoustic wave technologies, as well as other proximitysensor arrays or other elements for determining one or more points ofcontact with touch screen 112. In an exemplary embodiment, projectedmutual capacitance sensing technology is used, such as that found in theiPhone® and iPod Touch® from Apple Inc. of Cupertino, Calif.

A touch-sensitive display in some embodiments of touch screen 112 is,optionally, analogous to the multi-touch sensitive touchpads describedin the following U.S. Pat. Nos. 6,323,846 (Westerman et al.), 6,570,557(Westerman et al.), and/or 6,677,932 (Westerman), and/or U.S. PatentPublication 2002/0015024A1, each of which is hereby incorporated byreference in its entirety. However, touch screen 112 displays visualoutput from device 100, whereas touch-sensitive touchpads do not providevisual output.

A touch-sensitive display in some embodiments of touch screen 112 isdescribed in the following applications: (1) U.S. patent applicationSer. No. 11/381,313, “Multipoint Touch Surface Controller,” filed May 2,2006; (2) U.S. patent application Ser. No. 10/840,862, “MultipointTouchscreen,” filed May 6, 2004; (3) U.S. patent application Ser. No.10/903,964, “Gestures For Touch Sensitive Input Devices,” filed Jul. 30,2004; (4) U.S. patent application Ser. No. 11/048,264, “Gestures ForTouch Sensitive Input Devices,” filed Jan. 31, 2005; (5) U.S. patentapplication Ser. No. 11/038,590, “Mode-Based Graphical User InterfacesFor Touch Sensitive Input Devices,” filed Jan. 18, 2005, (6) U.S. patentapplication Ser. No. 11/228,758, “Virtual Input Device Placement On ATouch Screen User Interface,” filed Sep. 16, 2005; (7) U.S. patentapplication Ser. No. 11/228,700, “Operation Of A Computer With A TouchScreen Interface,” filed Sep. 16, 2005; (8) U.S. patent application Ser.No. 11/228,737, “Activating Virtual Keys Of A Touch-Screen VirtualKeyboard,” filed Sep. 16, 2005; and (9) U.S. patent application Ser. No.11/367,749, “Multi-Functional Hand-Held Device,” filed Mar. 3, 2006. Allof these applications are incorporated by reference herein in theirentirety.

Touch screen 112 optionally has a video resolution in excess of 100 dpi.In some embodiments, the touch screen has a video resolution ofapproximately 160 dpi. The user optionally makes contact with touchscreen 112 using any suitable object or appendage, such as a stylus, afinger, and so forth. In some embodiments, the user interface isdesigned to work primarily with finger-based contacts and gestures,which can be less precise than stylus-based input due to the larger areaof contact of a finger on the touch screen. In some embodiments, thedevice translates the rough finger-based input into a precisepointer/cursor position or command for performing the actions desired bythe user.

In some embodiments, in addition to the touch screen, device 100optionally includes a touchpad for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad is, optionally, a touch-sensitive surface that isseparate from touch screen 112 or an extension of the touch-sensitivesurface formed by the touch screen.

Device 100 also includes power system 162 for powering the variouscomponents. Power system 162 optionally includes a power managementsystem, one or more power sources (e.g., battery, alternating current(AC)), a recharging system, a power failure detection circuit, a powerconverter or inverter, a power status indicator (e.g., a light-emittingdiode (LED)) and any other components associated with the generation,management and distribution of power in portable devices.

Device 100 optionally also includes one or more optical sensors 164.FIG. 1A shows an optical sensor coupled to optical sensor controller 158in I/O subsystem 106. Optical sensor 164 optionally includescharge-coupled device (CCD) or complementary metal-oxide semiconductor(CMOS) phototransistors. Optical sensor 164 receives light from theenvironment, projected through one or more lenses, and converts thelight to data representing an image. In conjunction with imaging module143 (also called a camera module), optical sensor 164 optionallycaptures still images or video. In some embodiments, an optical sensoris located on the back of device 100, opposite touch screen display 112on the front of the device so that the touch screen display is enabledfor use as a viewfinder for still and/or video image acquisition. Insome embodiments, an optical sensor is located on the front of thedevice so that the user's image is, optionally, obtained for videoconferencing while the user views the other video conferenceparticipants on the touch screen display. In some embodiments, theposition of optical sensor 164 can be changed by the user (e.g., byrotating the lens and the sensor in the device housing) so that a singleoptical sensor 164 is used along with the touch screen display for bothvideo conferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more depth camera sensors175. FIG. 1A shows a depth camera sensor coupled to depth cameracontroller 169 in I/O subsystem 106. Depth camera sensor 175 receivesdata from the environment to create a three dimensional model of anobject (e.g., a face) within a scene from a viewpoint (e.g., a depthcamera sensor). In some embodiments, in conjunction with imaging module143 (also called a camera module), depth camera sensor 175 is optionallyused to determine a depth map of different portions of an image capturedby the imaging module 143. In some embodiments, a depth camera sensor islocated on the front of device 100 so that the user's image with depthinformation is, optionally, obtained for video conferencing while theuser views the other video conference participants on the touch screendisplay and to capture selfies with depth map data. In some embodiments,the depth camera sensor 175 is located on the back of device, or on theback and the front of the device 100. In some embodiments, the positionof depth camera sensor 175 can be changed by the user (e.g., by rotatingthe lens and the sensor in the device housing) so that a depth camerasensor 175 is used along with the touch screen display for both videoconferencing and still and/or video image acquisition.

Device 100 optionally also includes one or more contact intensitysensors 165. FIG. 1A shows a contact intensity sensor coupled tointensity sensor controller 159 in I/O subsystem 106. Contact intensitysensor 165 optionally includes one or more piezoresistive strain gauges,capacitive force sensors, electric force sensors, piezoelectric forcesensors, optical force sensors, capacitive touch-sensitive surfaces, orother intensity sensors (e.g., sensors used to measure the force (orpressure) of a contact on a touch-sensitive surface). Contact intensitysensor 165 receives contact intensity information (e.g., pressureinformation or a proxy for pressure information) from the environment.In some embodiments, at least one contact intensity sensor is collocatedwith, or proximate to, a touch-sensitive surface (e.g., touch-sensitivedisplay system 112). In some embodiments, at least one contact intensitysensor is located on the back of device 100, opposite touch screendisplay 112, which is located on the front of device 100.

Device 100 optionally also includes one or more proximity sensors 166.FIG. 1A shows proximity sensor 166 coupled to peripherals interface 118.Alternately, proximity sensor 166 is, optionally, coupled to inputcontroller 160 in I/O subsystem 106. Proximity sensor 166 optionallyperforms as described in U.S. patent application Ser. No. 11/241,839,“Proximity Detector In Handheld Device”; Ser. No. 11/240,788, “ProximityDetector In Handheld Device”; Ser. No. 11/620,702, “Using Ambient LightSensor To Augment Proximity Sensor Output”; Ser. No. 11/586,862,“Automated Response To And Sensing Of User Activity In PortableDevices”; and Ser. No. 11/638,251, “Methods And Systems For AutomaticConfiguration Of Peripherals,” which are hereby incorporated byreference in their entirety. In some embodiments, the proximity sensorturns off and disables touch screen 112 when the multifunction device isplaced near the user's ear (e.g., when the user is making a phone call).

Device 100 optionally also includes one or more tactile outputgenerators 167. FIG. 1A shows a tactile output generator coupled tohaptic feedback controller 161 in I/O subsystem 106. Tactile outputgenerator 167 optionally includes one or more electroacoustic devicessuch as speakers or other audio components and/or electromechanicaldevices that convert energy into linear motion such as a motor,solenoid, electroactive polymer, piezoelectric actuator, electrostaticactuator, or other tactile output generating component (e.g., acomponent that converts electrical signals into tactile outputs on thedevice). Contact intensity sensor 165 receives tactile feedbackgeneration instructions from haptic feedback module 133 and generatestactile outputs on device 100 that are capable of being sensed by a userof device 100. In some embodiments, at least one tactile outputgenerator is collocated with, or proximate to, a touch-sensitive surface(e.g., touch-sensitive display system 112) and, optionally, generates atactile output by moving the touch-sensitive surface vertically (e.g.,in/out of a surface of device 100) or laterally (e.g., back and forth inthe same plane as a surface of device 100). In some embodiments, atleast one tactile output generator sensor is located on the back ofdevice 100, opposite touch screen display 112, which is located on thefront of device 100.

Device 100 optionally also includes one or more accelerometers 168. FIG.1A shows accelerometer 168 coupled to peripherals interface 118.Alternately, accelerometer 168 is, optionally, coupled to an inputcontroller 160 in I/O subsystem 106. Accelerometer 168 optionallyperforms as described in U.S. Patent Publication No. 20050190059,“Acceleration-based Theft Detection System for Portable ElectronicDevices,” and U.S. Patent Publication No. 20060017692, “Methods AndApparatuses For Operating A Portable Device Based On An Accelerometer,”both of which are incorporated by reference herein in their entirety. Insome embodiments, information is displayed on the touch screen displayin a portrait view or a landscape view based on an analysis of datareceived from the one or more accelerometers. Device 100 optionallyincludes, in addition to accelerometer(s) 168, a magnetometer and a GPS(or GLONASS or other global navigation system) receiver for obtaininginformation concerning the location and orientation (e.g., portrait orlandscape) of device 100.

In some embodiments, the software components stored in memory 102include operating system 126, communication module (or set ofinstructions) 128, contact/motion module (or set of instructions) 130,graphics module (or set of instructions) 132, text input module (or setof instructions) 134, Global Positioning System (GPS) module (or set ofinstructions) 135, and applications (or sets of instructions) 136.Furthermore, in some embodiments, memory 102 (FIG. 1A) or 370 (FIG. 3 )stores device/global internal state 157, as shown in FIGS. 1A and 3 .Device/global internal state 157 includes one or more of: activeapplication state, indicating which applications, if any, are currentlyactive; display state, indicating what applications, views or otherinformation occupy various regions of touch screen display 112; sensorstate, including information obtained from the device's various sensorsand input control devices 116; and location information concerning thedevice's location and/or attitude.

Operating system 126 (e.g., Darwin, RTXC, LINUX, UNIX, OS X, iOS,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

Communication module 128 facilitates communication with other devicesover one or more external ports 124 and also includes various softwarecomponents for handling data received by RF circuitry 108 and/orexternal port 124. External port 124 (e.g., Universal Serial Bus (USB),FIREWIRE, etc.) is adapted for coupling directly to other devices orindirectly over a network (e.g., the Internet, wireless LAN, etc.). Insome embodiments, the external port is a multi-pin (e.g., 30-pin)connector that is the same as, or similar to and/or compatible with, the30-pin connector used on iPod® (trademark of Apple Inc.) devices.

Contact/motion module 130 optionally detects contact with touch screen112 (in conjunction with display controller 156) and othertouch-sensitive devices (e.g., a touchpad or physical click wheel).Contact/motion module 130 includes various software components forperforming various operations related to detection of contact, such asdetermining if contact has occurred (e.g., detecting a finger-downevent), determining an intensity of the contact (e.g., the force orpressure of the contact or a substitute for the force or pressure of thecontact), determining if there is movement of the contact and trackingthe movement across the touch-sensitive surface (e.g., detecting one ormore finger-dragging events), and determining if the contact has ceased(e.g., detecting a finger-up event or a break in contact).Contact/motion module 130 receives contact data from the touch-sensitivesurface. Determining movement of the point of contact, which isrepresented by a series of contact data, optionally includes determiningspeed (magnitude), velocity (magnitude and direction), and/or anacceleration (a change in magnitude and/or direction) of the point ofcontact. These operations are, optionally, applied to single contacts(e.g., one finger contacts) or to multiple simultaneous contacts (e.g.,“multitouch”/multiple finger contacts). In some embodiments,contact/motion module 130 and display controller 156 detect contact on atouchpad.

In some embodiments, contact/motion module 130 uses a set of one or moreintensity thresholds to determine whether an operation has beenperformed by a user (e.g., to determine whether a user has “clicked” onan icon). In some embodiments, at least a subset of the intensitythresholds are determined in accordance with software parameters (e.g.,the intensity thresholds are not determined by the activation thresholdsof particular physical actuators and can be adjusted without changingthe physical hardware of device 100). For example, a mouse “click”threshold of a trackpad or touch screen display can be set to any of alarge range of predefined threshold values without changing the trackpador touch screen display hardware. Additionally, in some implementations,a user of the device is provided with software settings for adjustingone or more of the set of intensity thresholds (e.g., by adjustingindividual intensity thresholds and/or by adjusting a plurality ofintensity thresholds at once with a system-level click “intensity”parameter).

Contact/motion module 130 optionally detects a gesture input by a user.Different gestures on the touch-sensitive surface have different contactpatterns (e.g., different motions, timings, and/or intensities ofdetected contacts). Thus, a gesture is, optionally, detected bydetecting a particular contact pattern. For example, detecting a fingertap gesture includes detecting a finger-down event followed by detectinga finger-up (liftoff) event at the same position (or substantially thesame position) as the finger-down event (e.g., at the position of anicon). As another example, detecting a finger swipe gesture on thetouch-sensitive surface includes detecting a finger-down event followedby detecting one or more finger-dragging events, and subsequentlyfollowed by detecting a finger-up (liftoff) event.

Graphics module 132 includes various known software components forrendering and displaying graphics on touch screen 112 or other display,including components for changing the visual impact (e.g., brightness,transparency, saturation, contrast, or other visual property) ofgraphics that are displayed. As used herein, the term “graphics”includes any object that can be displayed to a user, including, withoutlimitation, text, web pages, icons (such as user-interface objectsincluding soft keys), digital images, videos, animations, and the like.

In some embodiments, graphics module 132 stores data representinggraphics to be used. Each graphic is, optionally, assigned acorresponding code. Graphics module 132 receives, from applicationsetc., one or more codes specifying graphics to be displayed along with,if necessary, coordinate data and other graphic property data, and thengenerates screen image data to output to display controller 156.

Haptic feedback module 133 includes various software components forgenerating instructions used by tactile output generator(s) 167 toproduce tactile outputs at one or more locations on device 100 inresponse to user interactions with device 100.

Text input module 134, which is, optionally, a component of graphicsmodule 132, provides soft keyboards for entering text in variousapplications (e.g., contacts 137, e-mail 140, IM 141, browser 147, andany other application that needs text input).

GPS module 135 determines the location of the device and provides thisinformation for use in various applications (e.g., to telephone 138 foruse in location-based dialing; to camera 143 as picture/video metadata;and to applications that provide location-based services such as weatherwidgets, local yellow page widgets, and map/navigation widgets).

Applications 136 optionally include the following modules (or sets ofinstructions), or a subset or superset thereof:

-   -   Contacts module 137 (sometimes called an address book or contact        list);    -   Telephone module 138;    -   Video conference module 139;    -   E-mail client module 140;    -   Instant messaging (IM) module 141;    -   Workout support module 142;    -   Camera module 143 for still and/or video images;    -   Image management module 144;    -   Video player module;    -   Music player module;    -   Browser module 147;    -   Calendar module 148;    -   Widget modules 149, which optionally include one or more of:        weather widget 149-1, stocks widget 149-2, calculator widget        149-3, alarm clock widget 149-4, dictionary widget 149-5, and        other widgets obtained by the user, as well as user-created        widgets 149-6;    -   Widget creator module 150 for making user-created widgets 149-6;    -   Search module 151.    -   Video and music player module 152, which merges video player        module and music player module;    -   Notes module 153;    -   Map module 154; and/or    -   Online video module 155.

Examples of other applications 136 that are, optionally, stored inmemory 102 include other word processing applications, other imageediting applications, drawing applications, presentation applications,JAVA-enabled applications, encryption, digital rights management, voicerecognition, and voice replication.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, contacts module 137 are, optionally, used to manage an address bookor contact list (e.g., stored in application internal state 192 ofcontacts module 137 in memory 102 or memory 370), including: addingname(s) to the address book; deleting name(s) from the address book;associating telephone number(s), e-mail address(es), physicaladdress(es) or other information with a name: associating an image witha name; categorizing and sorting names; providing telephone numbers ore-mail addresses to initiate and/or facilitate communications bytelephone 138, video conference module 139, e-mail 140, or IM 141; andso forth.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, contact/motionmodule 130, graphics module 132, and text input module 134, telephonemodule 138 are optionally, used to enter a sequence of characterscorresponding to a telephone number, access one or more telephonenumbers in contacts module 137, modify a telephone number that has beenentered, dial a respective telephone number, conduct a conversation, anddisconnect or hang up when the conversation is completed. As notedabove, the wireless communication optionally uses any of a plurality ofcommunications standards, protocols, and technologies.

In conjunction with RF circuitry 108, audio circuitry 110, speaker 111,microphone 113, touch screen 112, display controller 156, optical sensor164, optical sensor controller 158, contact/motion module 130, graphicsmodule 132, text input module 134, contacts module 137, and telephonemodule 138, video conference module 139 includes executable instructionsto initiate, conduct, and terminate a video conference between a userand one or more other participants in accordance with user instructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, e-mail client module 140 includes executableinstructions to create, send, receive, and manage e-mail in response touser instructions. In conjunction with image management module 144,e-mail client module 140 makes it very easy to create and send e-mailswith still or video images taken with camera module 143.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, the instant messaging module 141 includes executableinstructions to enter a sequence of characters corresponding to aninstant message, to modify previously entered characters, to transmit arespective instant message (for example, using a Short Message Service(SMS) or Multimedia Message Service (MMS) protocol for telephony-basedinstant messages or using XMPP, SIMPLE, or IMPS for Internet-basedinstant messages), to receive instant messages, and to view receivedinstant messages. In some embodiments, transmitted and/or receivedinstant messages optionally include graphics, photos, audio files, videofiles and/or other attachments as are supported in an MMS and/or anEnhanced Messaging Service (EMS). As used herein, “instant messaging”refers to both telephony-based messages (e.g., messages sent using SMSor MMS) and Internet-based messages (e.g., messages sent using XMPP,SIMPLE, or IMPS).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, map module 154, and music playermodule, workout support module 142 includes executable instructions tocreate workouts (e.g., with time, distance, and/or calorie burninggoals); communicate with workout sensors (sports devices); receiveworkout sensor data; calibrate sensors used to monitor a workout; selectand play music for a workout; and display, store, and transmit workoutdata.

In conjunction with touch screen 112, display controller 156, opticalsensor(s) 164, optical sensor controller 158, contact/motion module 130,graphics module 132, and image management module 144, camera module 143includes executable instructions to capture still images or video(including a video stream) and store them into memory 102, modifycharacteristics of a still image or video, or delete a still image orvideo from memory 102.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, text input module 134,and camera module 143, image management module 144 includes executableinstructions to arrange, modify (e.g., edit), or otherwise manipulate,label, delete, present (e.g., in a digital slide show or album), andstore still and/or video images.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, and textinput module 134, browser module 147 includes executable instructions tobrowse the Internet in accordance with user instructions, includingsearching, linking to, receiving, and displaying web pages or portionsthereof, as well as attachments and other files linked to web pages.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, e-mail client module 140, and browser module 147,calendar module 148 includes executable instructions to create, display,modify, and store calendars and data associated with calendars (e.g.,calendar entries, to-do lists, etc.) in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, widget modules 149 aremini-applications that are, optionally, downloaded and used by a user(e.g., weather widget 149-1, stocks widget 149-2, calculator widget149-3, alarm clock widget 149-4, and dictionary widget 149-5) or createdby the user (e.g., user-created widget 149-6). In some embodiments, awidget includes an HTML (Hypertext Markup Language) file, a CSS(Cascading Style Sheets) file, and a JavaScript file. In someembodiments, a widget includes an XML (Extensible Markup Language) fileand a JavaScript file (e.g., Yahoo!Widgets).

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, and browser module 147, the widget creator module 150are, optionally, used by a user to create widgets (e.g., turning auser-specified portion of a web page into a widget).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, search module 151 includes executable instructions to search fortext, music, sound, image, video, and/or other files in memory 102 thatmatch one or more search criteria (e.g., one or more user-specifiedsearch terms) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, and browser module 147, video and musicplayer module 152 includes executable instructions that allow the userto download and play back recorded music and other sound files stored inone or more file formats, such as MP3 or AAC files, and executableinstructions to display, present, or otherwise play back videos (e.g.,on touch screen 112 or on an external, connected display via externalport 124). In some embodiments, device 100 optionally includes thefunctionality of an MP3 player, such as an iPod (trademark of AppleInc.).

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, and text input module134, notes module 153 includes executable instructions to create andmanage notes, to-do lists, and the like in accordance with userinstructions.

In conjunction with RF circuitry 108, touch screen 112, displaycontroller 156, contact/motion module 130, graphics module 132, textinput module 134, GPS module 135, and browser module 147, map module 154are, optionally, used to receive, display, modify, and store maps anddata associated with maps (e.g., driving directions, data on stores andother points of interest at or near a particular location, and otherlocation-based data) in accordance with user instructions.

In conjunction with touch screen 112, display controller 156,contact/motion module 130, graphics module 132, audio circuitry 110,speaker 111, RF circuitry 108, text input module 134, e-mail clientmodule 140, and browser module 147, online video module 155 includesinstructions that allow the user to access, browse, receive (e.g., bystreaming and/or download), play back (e.g., on the touch screen or onan external, connected display via external port 124), send an e-mailwith a link to a particular online video, and otherwise manage onlinevideos in one or more file formats, such as H.264. In some embodiments,instant messaging module 141, rather than e-mail client module 140, isused to send a link to a particular online video. Additional descriptionof the online video application can be found in U.S. Provisional PatentApplication No. 60/936,562, “Portable Multifunction Device, Method, andGraphical User Interface for Playing Online Videos,” filed Jun. 20,2007, and U.S. patent application Ser. No. 11/968,067, “PortableMultifunction Device, Method, and Graphical User Interface for PlayingOnline Videos,” filed Dec. 31, 2007, the contents of which are herebyincorporated by reference in their entirety.

Each of the above-identified modules and applications corresponds to aset of executable instructions for performing one or more functionsdescribed above and the methods described in this application (e.g., thecomputer-implemented methods and other information processing methodsdescribed herein). These modules (e.g., sets of instructions) need notbe implemented as separate software programs, procedures, or modules,and thus various subsets of these modules are, optionally, combined orotherwise rearranged in various embodiments. For example, video playermodule is, optionally, combined with music player module into a singlemodule (e.g., video and music player module 152, FIG. 1A). In someembodiments, memory 102 optionally stores a subset of the modules anddata structures identified above. Furthermore, memory 102 optionallystores additional modules and data structures not described above.

In some embodiments, device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough a touch screen and/or a touchpad. By using a touch screen and/ora touchpad as the primary input control device for operation of device100, the number of physical input control devices (such as push buttons,dials, and the like) on device 100 is, optionally, reduced.

The predefined set of functions that are performed exclusively through atouch screen and/or a touchpad optionally include navigation betweenuser interfaces. In some embodiments, the touchpad, when touched by theuser, navigates device 100 to a main, home, or root menu from any userinterface that is displayed on device 100. In such embodiments, a “menubutton” is implemented using a touchpad. In some other embodiments, themenu button is a physical push button or other physical input controldevice instead of a touchpad.

FIG. 1B is a block diagram illustrating exemplary components for eventhandling in accordance with some embodiments. In some embodiments,memory 102 (FIG. 1A) or 370 (FIG. 3 ) includes event sorter 170 (e.g.,in operating system 126) and a respective application 136-1 (e.g., anyof the aforementioned applications 137-151, 155, 380-390).

Event sorter 170 receives event information and determines theapplication 136-1 and application view 191 of application 136-1 to whichto deliver the event information. Event sorter 170 includes eventmonitor 171 and event dispatcher module 174. In some embodiments,application 136-1 includes application internal state 192, whichindicates the current application view(s) displayed on touch-sensitivedisplay 112 when the application is active or executing. In someembodiments, device/global internal state 157 is used by event sorter170 to determine which application(s) is (are) currently active, andapplication internal state 192 is used by event sorter 170 to determineapplication views 191 to which to deliver event information.

In some embodiments, application internal state 192 includes additionalinformation, such as one or more of: resume information to be used whenapplication 136-1 resumes execution, user interface state informationthat indicates information being displayed or that is ready for displayby application 136-1, a state queue for enabling the user to go back toa prior state or view of application 136-1, and a redo/undo queue ofprevious actions taken by the user.

Event monitor 171 receives event information from peripherals interface118. Event information includes information about a sub-event (e.g., auser touch on touch-sensitive display 112, as part of a multi-touchgesture). Peripherals interface 118 transmits information it receivesfrom I/O subsystem 106 or a sensor, such as proximity sensor 166,accelerometer(s) 168, and/or microphone 113 (through audio circuitry110). Information that peripherals interface 118 receives from I/Osubsystem 106 includes information from touch-sensitive display 112 or atouch-sensitive surface.

In some embodiments, event monitor 171 sends requests to the peripheralsinterface 118 at predetermined intervals. In response, peripheralsinterface 118 transmits event information. In other embodiments,peripherals interface 118 transmits event information only when there isa significant event (e.g., receiving an input above a predeterminednoise threshold and/or for more than a predetermined duration).

In some embodiments, event sorter 170 also includes a hit viewdetermination module 172 and/or an active event recognizer determinationmodule 173.

Hit view determination module 172 provides software procedures fordetermining where a sub-event has taken place within one or more viewswhen touch-sensitive display 112 displays more than one view. Views aremade up of controls and other elements that a user can see on thedisplay.

Another aspect of the user interface associated with an application is aset of views, sometimes herein called application views or userinterface windows, in which information is displayed and touch-basedgestures occur. The application views (of a respective application) inwhich a touch is detected optionally correspond to programmatic levelswithin a programmatic or view hierarchy of the application. For example,the lowest level view in which a touch is detected is, optionally,called the hit view, and the set of events that are recognized as properinputs are, optionally, determined based, at least in part, on the hitview of the initial touch that begins a touch-based gesture.

Hit view determination module 172 receives information related tosub-events of a touch-based gesture. When an application has multipleviews organized in a hierarchy, hit view determination module 172identifies a hit view as the lowest view in the hierarchy which shouldhandle the sub-event. In most circumstances, the hit view is the lowestlevel view in which an initiating sub-event occurs (e.g., the firstsub-event in the sequence of sub-events that form an event or potentialevent). Once the hit view is identified by the hit view determinationmodule 172, the hit view typically receives all sub-events related tothe same touch or input source for which it was identified as the hitview.

Active event recognizer determination module 173 determines which viewor views within a view hierarchy should receive a particular sequence ofsub-events. In some embodiments, active event recognizer determinationmodule 173 determines that only the hit view should receive a particularsequence of sub-events. In other embodiments, active event recognizerdetermination module 173 determines that all views that include thephysical location of a sub-event are actively involved views, andtherefore determines that all actively involved views should receive aparticular sequence of sub-events. In other embodiments, even if touchsub-events were entirely confined to the area associated with oneparticular view, views higher in the hierarchy would still remain asactively involved views.

Event dispatcher module 174 dispatches the event information to an eventrecognizer (e.g., event recognizer 180). In embodiments including activeevent recognizer determination module 173, event dispatcher module 174delivers the event information to an event recognizer determined byactive event recognizer determination module 173. In some embodiments,event dispatcher module 174 stores in an event queue the eventinformation, which is retrieved by a respective event receiver 182.

In some embodiments, operating system 126 includes event sorter 170.Alternatively, application 136-1 includes event sorter 170. In yet otherembodiments, event sorter 170 is a stand-alone module, or a part ofanother module stored in memory 102, such as contact/motion module 130.

In some embodiments, application 136-1 includes a plurality of eventhandlers 190 and one or more application views 191, each of whichincludes instructions for handling touch events that occur within arespective view of the application's user interface. Each applicationview 191 of the application 136-1 includes one or more event recognizers180. Typically, a respective application view 191 includes a pluralityof event recognizers 180. In other embodiments, one or more of eventrecognizers 180 are part of a separate module, such as a user interfacekit or a higher level object from which application 136-1 inheritsmethods and other properties. In some embodiments, a respective eventhandler 190 includes one or more of: data updater 176, object updater177, GUI updater 178, and/or event data 179 received from event sorter170. Event handler 190 optionally utilizes or calls data updater 176,object updater 177, or GUI updater 178 to update the applicationinternal state 192. Alternatively, one or more of the application views191 include one or more respective event handlers 190. Also, in someembodiments, one or more of data updater 176, object updater 177, andGUI updater 178 are included in a respective application view 191.

A respective event recognizer 180 receives event information (e.g.,event data 179) from event sorter 170 and identifies an event from theevent information. Event recognizer 180 includes event receiver 182 andevent comparator 184. In some embodiments, event recognizer 180 alsoincludes at least a subset of: metadata 183, and event deliveryinstructions 188 (which optionally include sub-event deliveryinstructions).

Event receiver 182 receives event information from event sorter 170. Theevent information includes information about a sub-event, for example, atouch or a touch movement. Depending on the sub-event, the eventinformation also includes additional information, such as location ofthe sub-event. When the sub-event concerns motion of a touch, the eventinformation optionally also includes speed and direction of thesub-event. In some embodiments, events include rotation of the devicefrom one orientation to another (e.g., from a portrait orientation to alandscape orientation, or vice versa), and the event informationincludes corresponding information about the current orientation (alsocalled device attitude) of the device.

Event comparator 184 compares the event information to predefined eventor sub-event definitions and, based on the comparison, determines anevent or sub-event, or determines or updates the state of an event orsub-event. In some embodiments, event comparator 184 includes eventdefinitions 186. Event definitions 186 contain definitions of events(e.g., predefined sequences of sub-events), for example, event 1(187-1), event 2 (187-2), and others. In some embodiments, sub-events inan event (187) include, for example, touch begin, touch end, touchmovement, touch cancellation, and multiple touching. In one example, thedefinition for event 1 (187-1) is a double tap on a displayed object.The double tap, for example, comprises a first touch (touch begin) onthe displayed object for a predetermined phase, a first liftoff (touchend) for a predetermined phase, a second touch (touch begin) on thedisplayed object for a predetermined phase, and a second liftoff (touchend) for a predetermined phase. In another example, the definition forevent 2 (187-2) is a dragging on a displayed object. The dragging, forexample, comprises a touch (or contact) on the displayed object for apredetermined phase, a movement of the touch across touch-sensitivedisplay 112, and liftoff of the touch (touch end). In some embodiments,the event also includes information for one or more associated eventhandlers 190.

In some embodiments, event definition 187 includes a definition of anevent for a respective user-interface object. In some embodiments, eventcomparator 184 performs a hit test to determine which user-interfaceobject is associated with a sub-event. For example, in an applicationview in which three user-interface objects are displayed ontouch-sensitive display 112, when a touch is detected on touch-sensitivedisplay 112, event comparator 184 performs a hit test to determine whichof the three user-interface objects is associated with the touch(sub-event). If each displayed object is associated with a respectiveevent handler 190, the event comparator uses the result of the hit testto determine which event handler 190 should be activated. For example,event comparator 184 selects an event handler associated with thesub-event and the object triggering the hit test.

In some embodiments, the definition for a respective event (187) alsoincludes delayed actions that delay delivery of the event informationuntil after it has been determined whether the sequence of sub-eventsdoes or does not correspond to the event recognizer's event type.

When a respective event recognizer 180 determines that the series ofsub-events do not match any of the events in event definitions 186, therespective event recognizer 180 enters an event impossible, eventfailed, or event ended state, after which it disregards subsequentsub-events of the touch-based gesture. In this situation, other eventrecognizers, if any, that remain active for the hit view continue totrack and process sub-events of an ongoing touch-based gesture.

In some embodiments, a respective event recognizer 180 includes metadata183 with configurable properties, flags, and/or lists that indicate howthe event delivery system should perform sub-event delivery to activelyinvolved event recognizers. In some embodiments, metadata 183 includesconfigurable properties, flags, and/or lists that indicate how eventrecognizers interact, or are enabled to interact, with one another. Insome embodiments, metadata 183 includes configurable properties, flags,and/or lists that indicate whether sub-events are delivered to varyinglevels in the view or programmatic hierarchy.

In some embodiments, a respective event recognizer 180 activates eventhandler 190 associated with an event when one or more particularsub-events of an event are recognized. In some embodiments, a respectiveevent recognizer 180 delivers event information associated with theevent to event handler 190. Activating an event handler 190 is distinctfrom sending (and deferred sending) sub-events to a respective hit view.In some embodiments, event recognizer 180 throws a flag associated withthe recognized event, and event handler 190 associated with the flagcatches the flag and performs a predefined process.

In some embodiments, event delivery instructions 188 include sub-eventdelivery instructions that deliver event information about a sub-eventwithout activating an event handler. Instead, the sub-event deliveryinstructions deliver event information to event handlers associated withthe series of sub-events or to actively involved views. Event handlersassociated with the series of sub-events or with actively involved viewsreceive the event information and perform a predetermined process.

In some embodiments, data updater 176 creates and updates data used inapplication 136-1. For example, data updater 176 updates the telephonenumber used in contacts module 137, or stores a video file used in videoplayer module. In some embodiments, object updater 177 creates andupdates objects used in application 136-1. For example, object updater177 creates a new user-interface object or updates the position of auser-interface object. GUI updater 178 updates the GUI. For example, GUIupdater 178 prepares display information and sends it to graphics module132 for display on a touch-sensitive display.

In some embodiments, event handler(s) 190 includes or has access to dataupdater 176, object updater 177, and GUI updater 178. In someembodiments, data updater 176, object updater 177, and GUI updater 178are included in a single module of a respective application 136-1 orapplication view 191. In other embodiments, they are included in two ormore software modules.

It shall be understood that the foregoing discussion regarding eventhandling of user touches on touch-sensitive displays also applies toother forms of user inputs to operate multifunction devices 100 withinput devices, not all of which are initiated on touch screens. Forexample, mouse movement and mouse button presses, optionally coordinatedwith single or multiple keyboard presses or holds; contact movementssuch as taps, drags, scrolls, etc. on touchpads; pen stylus inputs;movement of the device; oral instructions; detected eye movements;biometric inputs, and/or any combination thereof are optionally utilizedas inputs corresponding to sub-events which define an event to berecognized.

FIG. 2 illustrates a portable multifunction device 100 having a touchscreen 112 in accordance with some embodiments. The touch screenoptionally displays one or more graphics within user interface (UI) 200.In this embodiment, as well as others described below, a user is enabledto select one or more of the graphics by making a gesture on thegraphics, for example, with one or more fingers 202 (not drawn to scalein the figure) or one or more styluses 203 (not drawn to scale in thefigure). In some embodiments, selection of one or more graphics occurswhen the user breaks contact with the one or more graphics. In someembodiments, the gesture optionally includes one or more taps, one ormore swipes (from left to right, right to left, upward and/or downward),and/or a rolling of a finger (from right to left, left to right, upwardand/or downward) that has made contact with device 100. In someimplementations or circumstances, inadvertent contact with a graphicdoes not select the graphic. For example, a swipe gesture that sweepsover an application icon optionally does not select the correspondingapplication when the gesture corresponding to selection is a tap.

Device 100 optionally also include one or more physical buttons, such as“home” or menu button 204. As described previously, menu button 204 is,optionally, used to navigate to any application 136 in a set ofapplications that are, optionally, executed on device 100.Alternatively, in some embodiments, the menu button is implemented as asoft key in a GUI displayed on touch screen 112.

In some embodiments, device 100 includes touch screen 112, menu button204, push button 206 for powering the device on/off and locking thedevice, volume adjustment button(s) 208, subscriber identity module(SIM) card slot 210, headset jack 212, and docking/charging externalport 124. Push button 206 is, optionally, used to turn the power on/offon the device by depressing the button and holding the button in thedepressed state for a predefined time interval; to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed; and/or to unlock the device or initiate anunlock process. In an alternative embodiment, device 100 also acceptsverbal input for activation or deactivation of some functions throughmicrophone 113. Device 100 also, optionally, includes one or morecontact intensity sensors 165 for detecting intensity of contacts ontouch screen 112 and/or one or more tactile output generators 167 forgenerating tactile outputs for a user of device 100.

FIG. 3 is a block diagram of an exemplary multifunction device with adisplay and a touch-sensitive surface in accordance with someembodiments. Device 300 need not be portable. In some embodiments,device 300 is a laptop computer, a desktop computer, a tablet computer,a multimedia player device, a navigation device, an educational device(such as a child's learning toy), a gaming system, or a control device(e.g., a home or industrial controller). Device 300 typically includesone or more processing units (CPUs) 310, one or more network or othercommunications interfaces 360, memory 370, and one or more communicationbuses 320 for interconnecting these components. Communication buses 320optionally include circuitry (sometimes called a chipset) thatinterconnects and controls communications between system components.Device 300 includes input/output (I/O) interface 330 comprising display340, which is typically a touch screen display. I/O interface 330 alsooptionally includes a keyboard and/or mouse (or other pointing device)350 and touchpad 355, tactile output generator 357 for generatingtactile outputs on device 300 (e.g., similar to tactile outputgenerator(s) 167 described above with reference to FIG. 1A), sensors 359(e.g., optical, acceleration, proximity, touch-sensitive, and/or contactintensity sensors similar to contact intensity sensor(s) 165 describedabove with reference to FIG. 1A). Memory 370 includes high-speed randomaccess memory, such as DRAM, SRAM, DDR RAM, or other random access solidstate memory devices; and optionally includes non-volatile memory, suchas one or more magnetic disk storage devices, optical disk storagedevices, flash memory devices, or other non-volatile solid state storagedevices. Memory 370 optionally includes one or more storage devicesremotely located from CPU(s) 310. In some embodiments, memory 370 storesprograms, modules, and data structures analogous to the programs,modules, and data structures stored in memory 102 of portablemultifunction device 100 (FIG. 1A), or a subset thereof. Furthermore,memory 370 optionally stores additional programs, modules, and datastructures not present in memory 102 of portable multifunction device100. For example, memory 370 of device 300 optionally stores drawingmodule 380, presentation module 382, word processing module 384, websitecreation module 386, disk authoring module 388, and/or spreadsheetmodule 390, while memory 102 of portable multifunction device 100 (FIG.1A) optionally does not store these modules.

Each of the above-identified elements in FIG. 3 is, optionally, storedin one or more of the previously mentioned memory devices. Each of theabove-identified modules corresponds to a set of instructions forperforming a function described above. The above-identified modules orprograms (e.g., sets of instructions) need not be implemented asseparate software programs, procedures, or modules, and thus varioussubsets of these modules are, optionally, combined or otherwiserearranged in various embodiments. In some embodiments, memory 370optionally stores a subset of the modules and data structures identifiedabove. Furthermore, memory 370 optionally stores additional modules anddata structures not described above.

Attention is now directed towards embodiments of user interfaces thatare, optionally, implemented on, for example, portable multifunctiondevice 100.

FIG. 4A illustrates an exemplary user interface for a menu ofapplications on portable multifunction device 100 in accordance withsome embodiments. Similar user interfaces are, optionally, implementedon device 300. In some embodiments, user interface 400 includes thefollowing elements, or a subset or superset thereof:

-   -   Signal strength indicator(s) 402 for wireless communication(s),        such as cellular and Wi-Fi signals;    -   Time 404;    -   Bluetooth indicator 405;    -   Battery status indicator 406;    -   Tray 408 with icons for frequently used applications, such as:        -   Icon 416 for telephone module 138, labeled “Phone,” which            optionally includes an indicator 414 of the number of missed            calls or voicemail messages;        -   Icon 418 for e-mail client module 140, labeled “Mail,” which            optionally includes an indicator 410 of the number of unread            e-mails;        -   Icon 420 for browser module 147, labeled “Browser;” and        -   Icon 422 for video and music player module 152, also            referred to as iPod (trademark of Apple Inc.) module 152,            labeled “iPod;” and    -   Icons for other applications, such as:        -   Icon 424 for IM module 141, labeled “Messages;”        -   Icon 426 for calendar module 148, labeled “Calendar;”        -   Icon 428 for image management module 144, labeled “Photos;”        -   Icon 430 for camera module 143, labeled “Camera;”        -   Icon 432 for online video module 155, labeled “Online            Video;”        -   Icon 434 for stocks widget 149-2, labeled “Stocks;”        -   Icon 436 for map module 154, labeled “Maps;”        -   Icon 438 for weather widget 149-1, labeled “Weather;”        -   Icon 440 for alarm clock widget 149-4, labeled “Clock;”        -   Icon 442 for workout support module 142, labeled “Workout            Support;”        -   Icon 444 for notes module 153, labeled “Notes;” and        -   Icon 446 for a settings application or module, labeled            “Settings,” which provides access to settings for device 100            and its various applications 136.

It should be noted that the icon labels illustrated in FIG. 4A aremerely exemplary. For example, icon 422 for video and music playermodule 152 is labeled “Music” or “Music Player.” Other labels are,optionally, used for various application icons. In some embodiments, alabel for a respective application icon includes a name of anapplication corresponding to the respective application icon. In someembodiments, a label for a particular application icon is distinct froma name of an application corresponding to the particular applicationicon.

FIG. 4B illustrates an exemplary user interface on a device (e.g.,device 300, FIG. 3 ) with a touch-sensitive surface 451 (e.g., a tabletor touchpad 355, FIG. 3 ) that is separate from the display 450 (e.g.,touch screen display 112). Device 300 also, optionally, includes one ormore contact intensity sensors (e.g., one or more of sensors 359) fordetecting intensity of contacts on touch-sensitive surface 451 and/orone or more tactile output generators 357 for generating tactile outputsfor a user of device 300.

Although some of the examples that follow will be given with referenceto inputs on touch screen display 112 (where the touch-sensitive surfaceand the display are combined), in some embodiments, the device detectsinputs on a touch-sensitive surface that is separate from the display,as shown in FIG. 4B. In some embodiments, the touch-sensitive surface(e.g., 451 in FIG. 4B) has a primary axis (e.g., 452 in FIG. 4B) thatcorresponds to a primary axis (e.g., 453 in FIG. 4B) on the display(e.g., 450). In accordance with these embodiments, the device detectscontacts (e.g., 460 and 462 in FIG. 4B) with the touch-sensitive surface451 at locations that correspond to respective locations on the display(e.g., in FIG. 4B, 460 corresponds to 468 and 462 corresponds to 470).In this way, user inputs (e.g., contacts 460 and 462, and movementsthereof) detected by the device on the touch-sensitive surface (e.g.,451 in FIG. 4B) are used by the device to manipulate the user interfaceon the display (e.g., 450 in FIG. 4B) of the multifunction device whenthe touch-sensitive surface is separate from the display. It should beunderstood that similar methods are, optionally, used for other userinterfaces described herein.

Additionally, while the following examples are given primarily withreference to finger inputs (e.g., finger contacts, finger tap gestures,finger swipe gestures), it should be understood that, in someembodiments, one or more of the finger inputs are replaced with inputfrom another input device (e.g., a mouse-based input or stylus input).For example, a swipe gesture is, optionally, replaced with a mouse click(e.g., instead of a contact) followed by movement of the cursor alongthe path of the swipe (e.g., instead of movement of the contact). Asanother example, a tap gesture is, optionally, replaced with a mouseclick while the cursor is located over the location of the tap gesture(e.g., instead of detection of the contact followed by ceasing to detectthe contact). Similarly, when multiple user inputs are simultaneouslydetected, it should be understood that multiple computer mice are,optionally, used simultaneously, or a mouse and finger contacts are,optionally, used simultaneously.

FIG. 5A illustrates exemplary personal electronic device 500. Device 500includes body 502. In some embodiments, device 500 can include some orall of the features described with respect to devices 100 and 300 (e.g.,FIGS. 1A-4B). In some embodiments, device 500 has touch-sensitivedisplay screen 504, hereafter touch screen 504. Alternatively, or inaddition to touch screen 504, device 500 has a display and atouch-sensitive surface. As with devices 100 and 300, in someembodiments, touch screen 504 (or the touch-sensitive surface)optionally includes one or more intensity sensors for detectingintensity of contacts (e.g., touches) being applied. The one or moreintensity sensors of touch screen 504 (or the touch-sensitive surface)can provide output data that represents the intensity of touches. Theuser interface of device 500 can respond to touches based on theirintensity, meaning that touches of different intensities can invokedifferent user interface operations on device 500.

Exemplary techniques for detecting and processing touch intensity arefound, for example, in related applications: International PatentApplication Serial No. PCT/US2013/040061, titled “Device, Method, andGraphical User Interface for Displaying User Interface ObjectsCorresponding to an Application,” filed May 8, 2013, published as WIPOPublication No. WO/2013/169849, and International Patent ApplicationSerial No. PCT/US2013/069483, titled “Device, Method, and Graphical UserInterface for Transitioning Between Touch Input to Display OutputRelationships,” filed Nov. 11, 2013, published as WIPO Publication No.WO/2014/105276, each of which is hereby incorporated by reference intheir entirety.

In some embodiments, device 500 has one or more input mechanisms 506 and508. Input mechanisms 506 and 508, if included, can be physical.Examples of physical input mechanisms include push buttons and rotatablemechanisms. In some embodiments, device 500 has one or more attachmentmechanisms. Such attachment mechanisms, if included, can permitattachment of device 500 with, for example, hats, eyewear, earrings,necklaces, shirts, jackets, bracelets, watch straps, chains, trousers,belts, shoes, purses, backpacks, and so forth. These attachmentmechanisms permit device 500 to be worn by a user.

FIG. 5B depicts exemplary personal electronic device 500. In someembodiments, device 500 can include some or all of the componentsdescribed with respect to FIGS. 1A, 1B, and 3. Device 500 has bus 512that operatively couples I/O section 514 with one or more computerprocessors 516 and memory 518. I/O section 514 can be connected todisplay 504, which can have touch-sensitive component 522 and,optionally, intensity sensor 524 (e.g., contact intensity sensor). Inaddition, I/O section 514 can be connected with communication unit 530for receiving application and operating system data, using Wi-Fi,Bluetooth, near field communication (NFC), cellular, and/or otherwireless communication techniques. Device 500 can include inputmechanisms 506 and/or 508. Input mechanism 506 is, optionally, arotatable input device or a depressible and rotatable input device, forexample. Input mechanism 508 is, optionally, a button, in some examples.

Input mechanism 508 is, optionally, a microphone, in some examples.Personal electronic device 500 optionally includes various sensors, suchas GPS sensor 532, accelerometer 534, directional sensor 540 (e.g.,compass), gyroscope 536, motion sensor 538, and/or a combinationthereof, all of which can be operatively connected to I/O section 514.

Memory 518 of personal electronic device 500 can include one or morenon-transitory computer-readable storage mediums, for storingcomputer-executable instructions, which, when executed by one or morecomputer processors 516, for example, can cause the computer processorsto perform the techniques described below, including processes 700, 800,900, and 1100 (FIGS. 7A, 7B, 8A, 8B, 9, 11A, and 11B). Acomputer-readable storage medium can be any medium that can tangiblycontain or store computer-executable instructions for use by or inconnection with the instruction execution system, apparatus, or device.In some examples, the storage medium is a transitory computer-readablestorage medium. In some examples, the storage medium is a non-transitorycomputer-readable storage medium. The non-transitory computer-readablestorage medium can include, but is not limited to, magnetic, optical,and/or semiconductor storages. Examples of such storage include magneticdisks, optical discs based on CD, DVD, or Blu-ray technologies, as wellas persistent solid-state memory such as flash, solid-state drives, andthe like. Personal electronic device 500 is not limited to thecomponents and configuration of FIG. 5B, but can include other oradditional components in multiple configurations.

As used here, the term “affordance” refers to a user-interactivegraphical user interface object that is, optionally, displayed on thedisplay screen of devices 100, 300, and/or 500 (FIGS. 1A, 3, and 5A-5B).For example, an image (e.g., icon), a button, and text (e.g., hyperlink)each optionally constitute an affordance.

As used herein, the term “focus selector” refers to an input elementthat indicates a current part of a user interface with which a user isinteracting. In some implementations that include a cursor or otherlocation marker, the cursor acts as a “focus selector” so that when aninput (e.g., a press input) is detected on a touch-sensitive surface(e.g., touchpad 355 in FIG. 3 or touch-sensitive surface 451 in FIG. 4B)while the cursor is over a particular user interface element (e.g., abutton, window, slider, or other user interface element), the particularuser interface element is adjusted in accordance with the detectedinput. In some implementations that include a touch screen display(e.g., touch-sensitive display system 112 in FIG. 1A or touch screen 112in FIG. 4A) that enables direct interaction with user interface elementson the touch screen display, a detected contact on the touch screen actsas a “focus selector” so that when an input (e.g., a press input by thecontact) is detected on the touch screen display at a location of aparticular user interface element (e.g., a button, window, slider, orother user interface element), the particular user interface element isadjusted in accordance with the detected input. In some implementations,focus is moved from one region of a user interface to another region ofthe user interface without corresponding movement of a cursor ormovement of a contact on a touch screen display (e.g., by using a tabkey or arrow keys to move focus from one button to another button); inthese implementations, the focus selector moves in accordance withmovement of focus between different regions of the user interface.Without regard to the specific form taken by the focus selector, thefocus selector is generally the user interface element (or contact on atouch screen display) that is controlled by the user so as tocommunicate the user's intended interaction with the user interface(e.g., by indicating, to the device, the element of the user interfacewith which the user is intending to interact). For example, the locationof a focus selector (e.g., a cursor, a contact, or a selection box) overa respective button while a press input is detected on thetouch-sensitive surface (e.g., a touchpad or touch screen) will indicatethat the user is intending to activate the respective button (as opposedto other user interface elements shown on a display of the device).

As used in the specification and claims, the term “characteristicintensity” of a contact refers to a characteristic of the contact basedon one or more intensities of the contact. In some embodiments, thecharacteristic intensity is based on multiple intensity samples. Thecharacteristic intensity is, optionally, based on a predefined number ofintensity samples, or a set of intensity samples collected during apredetermined time period (e.g., 0.05, 0.1, 0.2, 0.5, 1, 2, 5, 10seconds) relative to a predefined event (e.g., after detecting thecontact, prior to detecting liftoff of the contact, before or afterdetecting a start of movement of the contact, prior to detecting an endof the contact, before or after detecting an increase in intensity ofthe contact, and/or before or after detecting a decrease in intensity ofthe contact). A characteristic intensity of a contact is, optionally,based on one or more of: a maximum value of the intensities of thecontact, a mean value of the intensities of the contact, an averagevalue of the intensities of the contact, a top 10 percentile value ofthe intensities of the contact, a value at the half maximum of theintensities of the contact, a value at the 90 percent maximum of theintensities of the contact, or the like. In some embodiments, theduration of the contact is used in determining the characteristicintensity (e.g., when the characteristic intensity is an average of theintensity of the contact over time). In some embodiments, thecharacteristic intensity is compared to a set of one or more intensitythresholds to determine whether an operation has been performed by auser. For example, the set of one or more intensity thresholdsoptionally includes a first intensity threshold and a second intensitythreshold. In this example, a contact with a characteristic intensitythat does not exceed the first threshold results in a first operation, acontact with a characteristic intensity that exceeds the first intensitythreshold and does not exceed the second intensity threshold results ina second operation, and a contact with a characteristic intensity thatexceeds the second threshold results in a third operation. In someembodiments, a comparison between the characteristic intensity and oneor more thresholds is used to determine whether or not to perform one ormore operations (e.g., whether to perform a respective operation orforgo performing the respective operation), rather than being used todetermine whether to perform a first operation or a second operation.

In some embodiments, a portion of a gesture is identified for purposesof determining a characteristic intensity. For example, atouch-sensitive surface optionally receives a continuous swipe contacttransitioning from a start location and reaching an end location, atwhich point the intensity of the contact increases. In this example, thecharacteristic intensity of the contact at the end location is,optionally, based on only a portion of the continuous swipe contact, andnot the entire swipe contact (e.g., only the portion of the swipecontact at the end location). In some embodiments, a smoothing algorithmis, optionally, applied to the intensities of the swipe contact prior todetermining the characteristic intensity of the contact. For example,the smoothing algorithm optionally includes one or more of: anunweighted sliding-average smoothing algorithm, a triangular smoothingalgorithm, a median filter smoothing algorithm, and/or an exponentialsmoothing algorithm. In some circumstances, these smoothing algorithmseliminate narrow spikes or dips in the intensities of the swipe contactfor purposes of determining a characteristic intensity.

The intensity of a contact on the touch-sensitive surface is,optionally, characterized relative to one or more intensity thresholds,such as a contact-detection intensity threshold, a light press intensitythreshold, a deep press intensity threshold, and/or one or more otherintensity thresholds. In some embodiments, the light press intensitythreshold corresponds to an intensity at which the device will performoperations typically associated with clicking a button of a physicalmouse or a trackpad. In some embodiments, the deep press intensitythreshold corresponds to an intensity at which the device will performoperations that are different from operations typically associated withclicking a button of a physical mouse or a trackpad. In someembodiments, when a contact is detected with a characteristic intensitybelow the light press intensity threshold (e.g., and above a nominalcontact-detection intensity threshold below which the contact is nolonger detected), the device will move a focus selector in accordancewith movement of the contact on the touch-sensitive surface withoutperforming an operation associated with the light press intensitythreshold or the deep press intensity threshold. Generally, unlessotherwise stated, these intensity thresholds are consistent betweendifferent sets of user interface figures.

An increase of characteristic intensity of the contact from an intensitybelow the light press intensity threshold to an intensity between thelight press intensity threshold and the deep press intensity thresholdis sometimes referred to as a “light press” input. An increase ofcharacteristic intensity of the contact from an intensity below the deeppress intensity threshold to an intensity above the deep press intensitythreshold is sometimes referred to as a “deep press” input. An increaseof characteristic intensity of the contact from an intensity below thecontact-detection intensity threshold to an intensity between thecontact-detection intensity threshold and the light press intensitythreshold is sometimes referred to as detecting the contact on thetouch-surface. A decrease of characteristic intensity of the contactfrom an intensity above the contact-detection intensity threshold to anintensity below the contact-detection intensity threshold is sometimesreferred to as detecting liftoff of the contact from the touch-surface.In some embodiments, the contact-detection intensity threshold is zero.In some embodiments, the contact-detection intensity threshold isgreater than zero.

In some embodiments described herein, one or more operations areperformed in response to detecting a gesture that includes a respectivepress input or in response to detecting the respective press inputperformed with a respective contact (or a plurality of contacts), wherethe respective press input is detected based at least in part ondetecting an increase in intensity of the contact (or plurality ofcontacts) above a press-input intensity threshold. In some embodiments,the respective operation is performed in response to detecting theincrease in intensity of the respective contact above the press-inputintensity threshold (e.g., a “down stroke” of the respective pressinput). In some embodiments, the press input includes an increase inintensity of the respective contact above the press-input intensitythreshold and a subsequent decrease in intensity of the contact belowthe press-input intensity threshold, and the respective operation isperformed in response to detecting the subsequent decrease in intensityof the respective contact below the press-input threshold (e.g., an “upstroke” of the respective press input).

In some embodiments, the device employs intensity hysteresis to avoidaccidental inputs sometimes termed “jitter,” where the device defines orselects a hysteresis intensity threshold with a predefined relationshipto the press-input intensity threshold (e.g., the hysteresis intensitythreshold is X intensity units lower than the press-input intensitythreshold or the hysteresis intensity threshold is 75%, 90%, or somereasonable proportion of the press-input intensity threshold). Thus, insome embodiments, the press input includes an increase in intensity ofthe respective contact above the press-input intensity threshold and asubsequent decrease in intensity of the contact below the hysteresisintensity threshold that corresponds to the press-input intensitythreshold, and the respective operation is performed in response todetecting the subsequent decrease in intensity of the respective contactbelow the hysteresis intensity threshold (e.g., an “up stroke” of therespective press input). Similarly, in some embodiments, the press inputis detected only when the device detects an increase in intensity of thecontact from an intensity at or below the hysteresis intensity thresholdto an intensity at or above the press-input intensity threshold and,optionally, a subsequent decrease in intensity of the contact to anintensity at or below the hysteresis intensity, and the respectiveoperation is performed in response to detecting the press input (e.g.,the increase in intensity of the contact or the decrease in intensity ofthe contact, depending on the circumstances).

For ease of explanation, the descriptions of operations performed inresponse to a press input associated with a press-input intensitythreshold or in response to a gesture including the press input are,optionally, triggered in response to detecting either: an increase inintensity of a contact above the press-input intensity threshold, anincrease in intensity of a contact from an intensity below thehysteresis intensity threshold to an intensity above the press-inputintensity threshold, a decrease in intensity of the contact below thepress-input intensity threshold, and/or a decrease in intensity of thecontact below the hysteresis intensity threshold corresponding to thepress-input intensity threshold. Additionally, in examples where anoperation is described as being performed in response to detecting adecrease in intensity of a contact below the press-input intensitythreshold, the operation is, optionally, performed in response todetecting a decrease in intensity of the contact below a hysteresisintensity threshold corresponding to, and lower than, the press-inputintensity threshold.

As used herein, the terms “open application” or “executing application”refer to a software application with retained state information (e.g.,as part of device/global internal state 157 and/or application internalstate 192). An open or executing application is, optionally, any one ofthe following types of applications:

-   -   an active application, which is currently displayed on a display        screen of the device that the application is being used on,    -   a background application (or background processes), which is not        currently displayed, but one or more processes for the        application are being processed by one or more processors; and    -   a suspended or hibernated application, which is not running, but        has state information that is stored in memory (volatile and        non-volatile, respectively) and that can be used to resume        execution of the application.

As used herein, the term “closed application” refers to softwareapplications without retained state information (e.g., state informationfor closed applications is not stored in a memory of the device).Accordingly, closing an application includes stopping and/or removingapplication processes for the application and removing state informationfor the application from the memory of the device. Generally, opening asecond application while in a first application does not close the firstapplication. When the second application is displayed and the firstapplication ceases to be displayed, the first application becomes abackground application.

Attention is now directed towards embodiments of user interfaces (“UI”)and associated processes that are implemented on an electronic device,such as portable multifunction device 100, device 300, or device 500.

FIGS. 6A-6I illustrate exemplary user interfaces for presenting activitytrends, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 7A, 7B, 8A, 8B, and 9 .

FIG. 6A depicts electronic device 600 displaying home user interface 604via display device 602. In some examples, electronic device 600 includesone or more features of devices 100, 300, or 500. Home user interface604 includes multiple affordances, each affordance for initiating adifferent application. For example, the multiple affordances includeactivity affordance 606 for initiating an activity application (e.g., anapplication corresponding to physical activity performed by a userassociated with electronic device 600).

As depicted in FIG. 6A, electronic device 600 receives user input 607corresponding to selection of activity affordance 606. User input 607can include a touch gesture, such as a tap gesture on activityaffordance 606, causing the activity application to be initiated (e.g.,display of a user interface of the activity application, such asinformation user interface 608 (depicted in FIG. 6B) or 90-day trendsuser interface 612 (depicted in FIGS. 6C-6F).

FIG. 6B depicts electronic device 600 displaying information userinterface 608 for an activity application (e.g., the activityapplication discussed above for FIG. 6A). Information user interface 608is an example of a first user interface displayed when initiating theactivity application. In some examples, information user interface 608is displayed at an initial time that a user navigates to the activityapplication after content to implement activity trends (e.g., techniquesdescribed in methods 700, 800, or 900) has been received by electronicdevice 600 (e.g., after an update or after an installation of theactivity application at a time after the content has been added to theactivity application).

In some examples, information user interface 608 is displayed inresponse to receiving user input (e.g., user input 607) corresponding toselection of an activity affordance (e.g., activity affordance 606). Itshould be recognized that other user interfaces (e.g., 90-day trendsuser interface 612, as depicted in FIG. 6C) can be displayed wheninitiating the activity application, such as when information userinterface 608 has been previously dismissed. In some examples, one ormore user inputs must be received before displaying information userinterface 608 and/or 90-day trends user interface 612.

Information user interface 608 provides information related to howactivity trends in the activity application work. For example, FIG. 6Bdepicts information user interface 608 including text that states“Closing your rings everyday will create trends with your activity data.See your comparison of the past 90 days with the past year.”

Information user interface 608 includes continue affordance 610.Selection of continue affordance 610 dismisses information userinterface 608 and causes a different user interface to be displayed(e.g., 90-day trends user interface 612, as depicted in FIG. 6C). Asdepicted in FIG. 6B, electronic device 600 receives user input 611corresponding to selection of continue affordance 610. User input 611can include a touch gesture, such as a tap gesture on continueaffordance 610.

FIG. 6C depicts electronic device 600 displaying an instance of 90-daytrends user interface 612 via display device 602 when an insufficientamount of data to identify a trend has been received for multipleactivity metrics. As used herein, a trend corresponds to a comparison ofdata within a first time period (e.g., 90 days) and data within a secondtime period (e.g., 365 days), where the first time period is includedwithin the second time period. In some examples, a trend can beidentified with less than a full time period. For example, instead ofrequiring 365 days of activity data for an activity metric, a trend forthe activity metric can be identified when there is at least 180 days ofactivity data for the activity data, where (1) the remaining dayswithout activity data are ignored when identifying the trend and (2) theshorter of the two time periods is potentially shortened to maintain asimilar percentage between the two percentages (e.g., when 180 days isreceived, the shorter of the two time periods can be 45). As shown, FIG.6C is a user interface shown after four days of activity is received fora user associated with electronic device 600. For clarity of theexamples discussed herein, a table is provided below to provide examplesof different trend classifications for different scenarios.

Difference between 90 day 365 day 90 day average and average average 365average Trend Assessment 90 100 −10 Negative 100 100 0 Neutral (in someexamples herein, classified as positive) 110 100 10 Positive

The instance of 90-day trends user interface 612 as depicted in FIG. 6Cincludes insufficient data portion 614 with header portion 616 andrepresentations for multiple activity metrics, such as moverepresentation 618. Header portion 616 includes a predicted amount oftime before a sufficient amount of data will have been received. Forexample, header portion 616 includes text stating: “Ready in: 26 days.”Such text indicates that it is estimated that the activity applicationwill have enough data to present activity trends via 90-day trends userinterface 612 in 26 days. The estimate can be calculated based onforecasting that sufficient information will be received each day forthe next 26 days, satisfying an amount of activity data to provideactivity trends after the 26 days. Header portion 616 includesinformation regarding why it will take 26 days to be ready (e.g., “Ittakes 30 days of activity to start your trends.”).

As indicated above, insufficient data portion 614 includes moverepresentation 618. Move representation 618 corresponds to activity datarelated to a move activity metric (e.g., an amount of movement that isdetermined for a user). Move representation 618 includes identificationinformation 618 a indicating that move representation 618 relates to themove activity metric (the “move” text), icon 618 b indicating that thereis insufficient activity data received for the move activity metric todetermine an activity trend for the move activity metric (the “−” with acircle around it), placeholder information 618 c indicating an averagevalue for move representation 618 is unavailable (the “−/− cal avg”text), and description 618 d (the “this trend measures the activecalories you burn” text). Other examples of representations for activitymetrics depicted in FIG. 6C include exercise, stand, and move minutes.Each of the other examples of representations include similar content asmove representation 618.

FIG. 6D depicts electronic device 600 displaying an instance of 90-daytrends user interface 612 via display device 602 when all activitymetrics have a negative trend within the last 90 days as compared to thelast 365 days. It should be recognized that trends might be overdifferent times from 90 days and 365 days (such as more or less than 90days and/or more or less than 365 days). In some examples, the trendsare based on rolling time periods. In some examples, a rolling timeperiod means that, as a new day is added to a time period, an oldest dayin the time period is removed. For example, a rolling time period of 90days means that at day 90 the rolling time period equals day 1 to day 90and at day 91 the rolling time period equals day 2 to day 91.

FIG. 6D depicts 90-day trends user interface 612 at least 30 days afterat least 30 days of activity data is received. For example, the instanceof 90-day trends user interface 612 depicted in FIG. 6D can be displayed26 days after the instance of 90-day trends user interface 612 depictedin FIG. 6C is displayed. In some examples, activity trends (e.g., moverepresentation 624) in 90-day trends user interface 612 are refresheddaily such that activity trends are updated each day. The instance of90-day trends user interface 612 depicted in FIG. 6D includes negativetrend portion 620 with overall coaching portion 622 and representationsfor multiple activity metrics, including move representation 624.

Overall coaching portion 622 includes text providing a summary of theincluded activity metrics. For example, overall coaching portion 622includes text stating. “Your trends need some attention. You've gotthis, John!”

The representations for multiple activity metrics included in negativetrend portion 620 each are associated with a different activity metricthat has been determined to have a negative trend (e.g., an average ofan activity metric for the past 90 days is less than an average of theactivity metric for the past 365 days). For example, negative trendportion 620 includes move representation 624. Move representation 624corresponds to activity data related to a move activity metric (e.g., anamount of movement that is determined for a user). Move representation624 includes identification information 624 a indicating that it relatesto the move activity metric (the “move” text), icon 624 b indicatingthat the move activity metric is trending down (the “V” with a circlearound it), average value 624 c indicating an average value for the moveactivity metric over the last 90 days (the “400 cal avg” text),comparison value 624 d indicating the difference between the averagevalue for the move activity metric over the last 90 days and an averagevalue for the move activity metric over the last 365 days (“−60”), andcoaching indication 624 e (the “Try to move around for 10 extra minutes”text). Other examples of representations depicted in FIG. 6D includeexercise, stand, and move minutes. Each of the other examples ofpresentations include similar content as move representation 618,including their own coaching indication (e.g., 626 e, 628 e, and 630 e).

In some examples, coaching indications are only provided torepresentations corresponding to activity metrics with a negative trendover the last 90 days as compared to the last 365 days. In suchexamples, coaching indications include a prediction for when a negativetrend will transition to a neutral or positive trend.

In some examples, coaching indications are modified based on an amountof time it would take for an average of the corresponding activitymetric to transition to a neutral or positive trend when forecasting anestimated increase (e.g., 10% per day). In some examples, the estimatedincrease can be capped based on a threshold for the correspondingactivity metric (e.g., an estimated increase for standing cannot cause astand goal of greater than 14 hours). In some examples, the amount oftime affects how the coaching indications are modified. For example:when the amount of time is less than a week, a coaching indicationincludes a prediction with the amount of time; when the amount of timeis more than a week and less than two weeks, a coaching indicationincludes a prediction with the amount of time rounded to a single week;when the amount of time is more than two weeks, a coaching indicationdoes not include a prediction of time. In some examples, differentactivity metrics use a different estimated increase.

In some examples, forecasting includes simulating the estimated increaseby: (1) forming a histogram associated with activity data for each of ashorter time period (e.g., the last 90 days) and a longer time period(e.g., the last 365 days) (e.g., each bin in the histogram correspondingto an average of activity data for a particular activity metric for adifferent day); (2) removing an oldest bin from the histogram; (3)adding a new bin to the histogram for the next day with a valuecorresponding to a value of activity data for a particular activitymetric for a current day and the estimated increase (e.g., if the valuefor the current day is 10 and the estimated increase is 1 (e.g., 10% ofthe value for the current day), the value for the new bin would be 11instead of 10); and (4) repeating 2 and 3 until the correspondingactivity metric transitions to a neutral or positive trend. In someexamples, when repeating 3, the estimated increase can be the same foreach additional day (e.g., based on example above, if the estimatedincrease is 1 and a value for a previous day is 11, the value for acurrent day would be 12), become zero after the first day (e.g., basedon example above, if the estimated increase becomes 9 after the firstday and a value for a previous day is 11, the value for a current daywould be 11 instead of continuing to increase to 12), or change each daybased on some function (e.g., f(x)=1/x).

In some examples, coaching indications are modified based on a recenttrend within the last 90 days, such as the last 15 days. In one example,the recent trend is determined using the Mann-Kendall (MK) test to lookat pairs of data in a given data set to identify whether a monotonictrend is present.

For clarity of the examples discussed above, a table is provided belowto provide examples of different coaching indications for differentscenarios with a description of why the coaching indication is what itis.

Explanation of coaching Trend classification Example coaching indicationindication Positive trend for 90/365 and “Getting better every day,Based on having a positive recently positive within 90 keep it up!”trend and recently positive, a coaching indication should encouragesimilar behavior in the future. Positive trend for 90/365 and “While youare above average Based on having a positive recently negative within 90for the last 90 days, you are trend but recently negative, starting tolose some ground.” a coaching indication should recognize the positivetrend but be more cautionary due to the recent negative trend. Negativetrend for 90/365 but “Keep doing what you are Based on having a negativerecently positive within 90 doing and you will be back trend butrecently positive, to your yearly average in a coaching indicationshould no time.” recognize that the user is improving. Negative trendfor 90/365 and “Don't forget to stand for one Based on having a negativerecently negative within 90 minute per hour throughout the trend andrecently negative, day, you are getting farther a coaching indicationshould from your average lately.” identify that a user is fallingfarther behind. Negative trend for 90/365 that “Try to move around for10 Based on being able to can transition to a positive extra minutes forthe next 3 transition within a week, a trend within a week if to daysand you will be right coaching indication should maintain a 10% increasein back to your yearly average.” identify a number of days average valueas compared to it takes to transition to a the last 90 days positivetrend with an estimated increase. Negative trend for 90/365 that “Walkan extra 10 minutes Based on being able to can transition to a positiveeach day and you'll be back transition longer than a trend longer than aweek but on track in 1 week.” week but within a few within a few weeksif maintain weeks, a coaching a 10% increase in average indicationshould identify a value as compared to the last way for a user to reachthe 90 days yearly average but round to the nearest week. Negative trendfor 90/365 that “Let's get back to the swing Based on being able to cantransition to a positive of things and walk a couple transition longerthan a trend over a few weeks if of minutes each day.” few weeks, acoaching maintain a 10% increase in indication should not average valueas compared to include any particular way the last 90 days to improve,such as a number of days or even an amount of activity per day.

FIG. 6E depicts electronic device 600 displaying an instance of 90-daytrends user interface 612 via display device 602 when some activitymetrics have a positive trend and other activity metrics have a negativetrend within the last 90 days as compared to the last 365 days. FIG. 6Edepicts 90-day trends user interface 612 at least 30 days after at least30 days of activity data is received. The instance of 90-day trends userinterface 612 depicted in FIG. 6E includes positive trend portion 632and negative trend portion 638, each with an overall coaching indicationfor the respective portion (e.g., overall coaching indication 634 andoverall coaching indication 640). In one example, overall coachingindication 634 for positive trend portion 632 includes the text “Keep itgoing” and overall coaching indication 640 for negative trend portion638 includes the text “Make it happen”). In some examples, the instanceof 90-day trends user interface 612 depicted in FIG. 6E (or anyinstances of 90-day trends user interface 612) includes an insufficientdata portion (not illustrated, but similar to insufficient data portion614 in the instance of 90-day trends user interface 612 depicted in FIG.6C) for one or more activity metrics with an insufficient amount ofcorresponding data. In one example, the insufficient data portion isbelow negative trend portion 638.

As mentioned above, the instance of 90-day trends user interface 612 asdepicted in FIG. 6E includes positive trend portion 632 withrepresentations for multiple activity metrics that have each beendetermined to be trending up or neutral (e.g., an average of an activitymetric for the past 90 days is equal to or greater than an average ofthe activity metric for the past 365 days). For example, positive trendportion 632 includes move representation 636. Move representation 636corresponds to activity data related to a move activity metric (e.g., anamount of movement that is determined for a user). Move representation636 includes identification information 636 a indicating that it relatesto the move activity metric (the “move” text), icon 636 b indicatingthat the move activity metric has a positive trend over the last 90 daysas compared to the last 365 days (the “

” with a circle around it), and average value 636 c indicating that themove activity metric has averaged 460 calories over the last 90 days(the “460 cal avg” text).

It should be recognized that the move representation, when in positivetrend portion 632, does not include a comparison value indicating thedifference between the average value for the move activity metric overthe last 90 days and an average value for the move activity metric overthe last 365 days and/or a coaching indication while both such contentis provided for activity metrics in negative trend portion 638. In someexamples, only providing the difference and/or the coaching indicationin negative trend portion 638 allows a system to not push users intothinking they need to keep increasing their trend. Similarly,classifying equal as positive, allows a system to not push users intothinking they need to keep increasing their trend.

Other examples of representations of activity metrics in positive trendportion 632 depicted in FIG. 6E include exercise, move minutes, walkingspeed, workout intensity, and flights climbed. While each of the otherexamples of representations of activity metrics in positive trendportion 632 include similar content as move representation 636, itshould be recognized that different representations sometimes havedifferent units of measure. For example, an exercise activityrepresentation, as depicted in FIG. 6E, includes text indicating thatexercise activity metric averaged 36 minutes per day for the last 90days.

As mentioned above, the instance of 90-day trends user interface 612 asdepicted in FIG. 6E includes negative trend portion 638 withrepresentations for multiple activity metrics that are each associatedwith a different activity metric that has been determined to have anegative trend (e.g., an average of an activity metric for the past 90days is less than an average of the activity metric for the past 365days). For example, negative trend portion 638 includes standrepresentation 642. Stand representation 642 corresponds to activitydata related to a stand activity metric (e.g., a number of hours per daywhere a user has determined to have stood for at least one hour). Standrepresentation 642 includes identification information 642 a indicatingthat it relates to the stand activity metric (the “stand” text), icon642 b indicating that the stand activity metric has a negative trendover the last 90 days as compared to the last 365 days (the “V” with acircle around it), average value 642 c indicating that the standactivity metric has averaged 10 hours per day over the last 90 days (the“10 hr avg” text), comparison value 642 d indicating the differencebetween the average value for the stand activity metric over the last 90days and an average value for the stand activity metric over the last365 days (“−2”), and coaching indication 642 e (the “Don't forget tostand for one minute per hour throughout the day” text). The otherexample of a representation in negative trend portion 638 depicted inFIG. 6E is walking distance representation 644. Walking distancerepresentation 644 includes similar content as stand representation 642,including its own coaching indication (644 e).

It should be recognized that the order within each portion (e.g.,positive trend portion 632 and negative trend portion 638) maintains theorder of representations as provided in instances discussed above. Arepresentation not included in one of the portions continues the orderin another portion. For example, the order in FIG. 6D is move, exercise,stand, and move minutes and the order in positive trend portion 632 ismove, exercise, and move minutes, with stand missing from positive trendportion 632 because move minutes did not have a positive trend. In FIG.6D, it can be seen that stand is the first representation in negativetrend portion 638.

In some examples, one or more icons in positive trend portion 632 (e.g.,636 b) (e.g., in some examples, all of the icons in positive trendportion 632, either sequentially or at the same time) are animated(e.g., bounce in an upward direction) in response to displaying theinstance of 90-day trends user interface 612 depicted in FIG. 6E. Aftera time threshold (e.g., zero or more; in some examples, non-zero) afteranimating the one or more icons in positive trend portion 632 haspassed, one or more icons in negative trend portion 638 (e.g., 642 b)(e.g., in some examples, all of the icons in negative trend portion 638,either sequentially or at the same time) are animated (e.g., bounce in adownward direction). By animating icons associated with negative trendportion 638 after animating icons associated with positive trend portion632, the instance of 90-day trends user interface 612 as depicted inFIG. 6E can draw emphasis to representations in negative trend portion638.

FIG. 6F depicts electronic device 600 displaying an instance of 90-daytrends user interface 612 via display device 602 when all activitymetrics have a positive trend within the last 90 days as compared to thelast 365 days. FIG. 6F depicts 90-day trends user interface 612 at least30 days after at least 30 days of activity data is received. Theinstance of 90-day trends user interface 612 depicted in FIG. 6Fincludes positive trend portion 646 and an overall coaching indicationstating “You're doing great!”

Positive trend portion 646 includes representations for multipleactivity metrics that have each been determined to be neutral orpositive (e.g., an average of an activity metric for the past 90 days isequal to or greater than an average of the activity metric for the past365 days). For example, positive trend portion 646 includes exerciserepresentation 648 and fitness levels representation 650. Exerciserepresentation 648 corresponds to activity data related to an exerciseactivity metric (e.g., an amount of time for which a user has beendetected exercising). Fitness levels representation 650 corresponds toactivity data related to a different exercise metric (e.g., a determinedworkout intensity for a user). It should be recognized that fitnesslevels representation 650 has not been displayed in other instances of90-day trends user interface 612 described above. This is illustratingthat some representations might only be displayed when there is at leastsome activity data received for a respective activity metric or there isenough activity data received for the respective activity metric toidentify a trend (e.g., 37 VO₂ max avg). This allows for metrics thatare often used to always show some representation (e.g., sometimes anull value) and other metrics that are not often used (or that requirespecial equipment) to only show when either some activity data has beenreceived or enough activity data has been received to provide a trend.

As depicted in FIG. 6F, electronic device 600 receives user input 649corresponding to selection of exercise representation 648. User input649 can include a touch gesture, such as a tap gesture on exerciserepresentation 648, causing a detailed activity metric user interfacecorresponding to exercise representation 648 to be displayed (e.g.,detailed exercise user interface 652, as depicted in FIG. 6G).

FIG. 6G depicts electronic device 600 displaying detailed exercise userinterface 652. In some examples, detailed exercise user interface 652 isdisplayed in response to receiving user input (e.g., user input 649)corresponding to selection of exercise representation 648. In someexamples, one or more user inputs must be received before displayingdetailed exercise user interface 652. It should be recognized that otherdetailed activity metric user interfaces can be displayed when otheractivity metric representations are selected, the other detailedactivity metric user interfaces corresponding to whichever activitymetric representation is selected.

Detailed exercise user interface 652 includes identification information654, indicating the activity metric that detailed exercise userinterface 652 corresponds. For example, identification information 654states that detailed exercise user interface 652 corresponds to anexercise activity metric.

Detailed exercise user interface 652 includes summary portion 656.Summary portion 656 includes textual representation 656 a indicatingwhether the exercise activity metric is trending down (e.g., an averageof the last 90 days is less than an average of the last 365 days) (wheretextual representation would be “trending down,” as illustrated),trending up (e.g., an average of the last 90 days is more than anaverage of the last 365 days) (where textual representation would be“trending up”), or trending neutral (e.g., an average of the last 90days is equal to an average of the last 365 days) (where textualrepresentation would be “staying consistent”). It should be recognizedthat trending neutral and trending up can be grouped together such thata system does not distinguish between the two, and instead uses thetrending up for when the trend is up or neutral. Summary portion 656includes icon 656 b indicating that the exercise activity metric has apositive trend over the last 90 days as compared to the last 365 days(the “

” with a circle around it). Summary portion 656 includes average value656 c indicating that the exercise activity metric has averaged 36minutes per day over the last 90 days (the “36 min avg” text). Summaryportion 656 includes difference indicator 656 d indicating a differencebetween an average of the last 90 days and an average of the last 365days (“+3”). Summary portion 656 includes summary information 656 e witha textual equivalent of icon 656 b. Summary portion 656 includescoaching indication 656 f indicating a suggestion for the exerciseactivity metric going forward. As depicted in FIG. 6G, coachingindication 656 f states “Keep it going, John!,” reflecting that theexercise activity metric is trending upward. It should be recognizedthat summary portion 656 can include a subset of what was describedabove (e.g., summary portion 656 might not include textualrepresentation 656 a).

Detailed exercise user interface 652 includes weekly representation 658to visually represent activity data for the exercise activity metricover the last 365 days. In some examples, such as depicted in FIG. 6G,weekly representation 658 is a bar graph with x-axis corresponding totime (e.g., weeks over the last 365 days) and y-axis corresponding to anaverage value for the exercise activity metric over either the last 90days or the last 365 days. In such examples, weekly representation 658is divided into weeks using a bar for each week (e.g., 52 bars). In someexamples, the x-axis of weekly representation 658 is labeled by monthand the range of the y-axis is from 0 to a maximum average value overthe last 365 days (e.g., 40, as depicted in FIG. 6G).

As depicted in FIG. 6G in weekly representation 658, bars associatedwith time periods within the last 90 days are visually distinguished(e.g., different patterns or different colors) from bars associated withtime periods within the last 365 days. In one example, the barsassociated with the last 90 days are green while the bars associatedwith the last 365 days are gray. When a week does not have anycorresponding activity data, a bar is not displayed for the week (e.g.,51 bars will be displayed instead of 52). In some examples, weeklyrepresentation 658 includes an additional indication to separaterepresentations corresponding to the last 90 days and representationscorresponding to the last 365 days but not the last 90 days. Forexample, in FIG. 6G, vertical line 658 c is inserted separating the twogroups of bars.

Weekly representation 658 includes 90-day average representation 658 aand 365-day average representation 658 b, where 90-day averageindication 658 a indicates an average for the last 90 days and 365-dayaverage representation 658 b indicates an average for the last 365 days(including the last 90 days). As depicted in FIG. 6G, each of 90-dayaverage representation 658 a and 365-day average representation 658 b isa visually distinct line at a vertical location corresponding to a valueof the corresponding average (e.g., because the average for the last 90days is greater than the average for the last 365 days, 90-day averagerepresentation 658 a is arranged at a vertical location higher than365-day average representation 658 b). In some examples, 90-day averagerepresentation 658 a includes an indication regarding whether theaverage for the last 90 days is equal to or greater than the average forthe last 365 days. For

example, as depicted in FIG. 6G, 90-day average representation 658 aincludes “

,” indicating that the average for the last 90 days is equal to orgreater than the average for the last 365 days. Similarly, if theaverage for the last 90 days is lower than the average for the last 365days, 90-day average representation 658 a can include “V.”

Detailed exercise user interface 652 includes daily averagesrepresentation 660 to compare activity data for the exercise activitymetric for particular days of a week over the last 90 days and the last365 days. In some examples, such as depicted in FIG. 6G, daily averagesrepresentation 660 includes a visual representation for comparing theactivity data (e.g., a bar graph with x-axis corresponding to differentdays of the week and y-axis corresponding to an average value for theexercise activity metric over the last 90 days and the last 365 days).In such examples, the range of the y-axis is from 0 to a maximum averagevalue over the last 365 days (e.g., 40, as depicted in FIG. 6G).

As depicted in FIG. 6G in daily averages representation 660, barsassociated with time periods corresponding to the last 90 days arevisually distinguished (e.g., different patterns or different colors)from bars associated with time periods corresponding to the last 365days. In one example, the bars corresponding to the last 90 days aregreen while the bars corresponding to the last 365 days are gray. Asdepicted in FIG. 6G in weekly representation 658, bars associated withtime periods (e.g., days within a week or hours within a day) within thelast 90 days are paired (e.g., adjacent with no interveningrepresentations) with bars associated with corresponding time periodswithin the last 365 days (e.g., a bar associated with Mondays within thelast 90 days is paired with a bar associated with Mondays within thelast 365 days.

Daily averages representation 660 includes textual representations(e.g., 660 a and 660 b) to correspond to the visual representation. Forexample, as depicted in FIG. 6A, daily averages representation 660includes a table under the visual representation, with numberscorresponding to the bar graph, such as 32 and 38 being located such asto appear to corresponding to the Monday section of the bar graph. Insome examples, numbers corresponding to the last 90 days are on a firstline of the table and numbers corresponding to the last 365 days are ona second line, under the first line. In some examples, numberscorresponding to the last 90 days are visually distinct (e.g., differentpatterns or different colors) from numbers corresponding to the last 365days. In one example, the numbers for the last 90 days are green whilethe numbers for the last 365 days are gray.

It should be recognized that some detailed activity metric userinterfaces might not include a daily averages representation, such asdetailed activity metric user interfaces corresponding to an action notoften performed every day (e.g., running speed). For example, an actionrelated to exercising can, instead of a daily averages representation,include a representation to compare activity data for an activity metricfor a particular time period (other than days of a week) over the last90 days and the last 365 days, such as hour, week, or month.

Detailed exercise user interface 652 includes exercise rings closedrepresentation 662 to compare an activity metric associated with butdifferent from the exercise activity metric. For example, exercise ringsclosed representation 662 relates to exercise rings closed, which is anactivity metric corresponding to a predefined or user-defined thresholdof an amount of exercise per day. In one example, exercise rings closedis associated with the exercise activity metric because an exercise ringcloses based on the exercise activity metric exceeding a threshold in agiven day.

Exercise rings closed representation 662 includes 90 days representation662 a and 365 days representation 662 b. 90 days representation 662 aincludes a textual representation of a number of days out of the last 90days that a user closed their exercise rings (e.g., “79/90 Days”) and apercentage for the number of days out of the last 90 days (e.g., “88%).365 days representation 662 b includes a textual representation of anumber of days out of the last 365 days that a user closed theirexercise rings (e.g., “284/365 Days”) and a percentage for the number ofdays out of the last 365 days (e.g., “77%). In some examples, 90 daysrepresentation 662 a is visually distinguished from 365 daysrepresentation 662 b (e.g., 90 days representation 662 a is green and365 days representation 662 b is gray).

FIG. 6H depicts electronic device 664 displaying ready-to-user userinterface 670 via display device 668 when activity trends (e.g., such asdepicted in FIG. 6D) are ready to be viewed on a second device (e.g.,electronic device 600). In some examples, electronic device 664 includesone or more features of devices 100, 300, 500, or 600. In some examples,ready-to-user user interface 670 includes positive trend portion 674,with display of multiple representations for different activity metrics(e.g., move representation or exercise representation). As depicted inFIG. 6H, each representation includes an identification of an activitymetric corresponding to the representation (e.g., “Move”), an iconcorresponding to a comparison of the activity metric for the last 90days as compared to the activity metric for the last 365 days (e.g.,icon with “

”), and a value corresponding to a summary of the activity metric forthe last 90 days (e.g., “460 cal avg”). In ready-to-user user interface670 as depicted in FIG. 6H, all activity metrics have a positive trendwithin the last 90 days as compared to the last 365 days. It should berecognized that this is just an example and other combinations of allnegative trends or a mix of some positive trends and some negativetrends are possible.

FIG. 6I depicts electronic device 664 displaying mid-month-update userinterface 678 via display device 668 when activity trends (e.g., such asdepicted in FIG. 6D) are available to be viewed on a second device(e.g., electronic device 600). In some examples, mid-month-update userinterface 678 is pushed to be displayed via display device 668 (e.g.,from electronic device 600) once per a particular time period (e.g., amonth). However, it should be recognized that mid-month-update userinterface 678 can be caused to be displayed at a different rate.

In some examples, mid-month-update user interface 678 includes positivetrend portion 682 and negative trend portion 684, each with display ofmultiple representations for different activity metrics (e.g., moverepresentation or exercise representation). As depicted in FIG. 6I, eachrepresentation in positive trend portion 682 includes an identificationof an activity metric corresponding to the representation (e.g.,“Move”), an icon corresponding to a comparison of the activity metricfor the last 90 days as compared to the activity metric for the

last 365 days (e.g., icon with “

”), and a value corresponding to the comparison (e.g., “460 cal avg”).As depicted in FIG. 6I, each representation in negative trend portion684 includes an identification of an activity metric corresponding tothe representation (e.g., “Move minutes”), an icon corresponding to acomparison of the activity metric for the last 90 days as compared tothe activity metric for the last 365 days (e.g., icon with “V”), a valuecorresponding to a summary of the activity metric for the last 90 days(e.g., “30 min avg”), and a difference between the summary of theactivity metric for the last 90 days and a summary of the activitymetric for the last 365 days (e.g., (“−4”).

In mid-month-update user interface 678 as depicted in FIG. 6I, someactivity metrics have a positive trend and other activity metrics have anegative trend within the last 90 days as compared to the last 365 days.It should be recognized that this is just an example and othercombinations of all positive trends or all negative trends are possible.

FIGS. 7A-7B are a flow diagram illustrating method 700 for presentingactivity trends (e.g., organizing activity metrics by trends (e.g.,upwards/downwards) over time) using an electronic device in accordancewith some embodiments. Method 700 relates to displaying a user interface(e.g., 90-day trend home page) with trend representation(s), eachrepresentation corresponding to a different activity metric, whereplacement of a trend representation is based on whether the trendrepresentation is determined to currently be a first classification(e.g., no change or positive) or a second classification (e.g.,negative). Method 700 is performed at a device (e.g., 100, 300, 500,600, 664) with a display device. Some operations in method 700 are,optionally, combined, the orders of some operations are, optionally,changed, and some operations are, optionally, omitted.

As described below, method 700 provides an intuitive way for presentingactivity trends. The method reduces the cognitive burden on a user forpresenting activity trends, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to identify activity trends faster and more efficientlyconserves power and increases the time between battery charges.

At 702, the device (e.g., 600, 664) receives activity data correspondingto a first activity metric (e.g., data corresponding to a measured levelof activity for a user of the electronic device (e.g., data for activityperformed by the user while wearing the electronic device)) for a firsttime period (e.g., 3 months).

At 704, the device receives activity data corresponding to the firstactivity metric for a second time period (e.g., 1 year) different fromthe first period of time.

At 706, the devices receives a request (e.g., 607 or 611) to display afirst user interface (e.g., 612) (e.g., user interface that includescomparisons of activity data for a plurality of activity metrics).

At 708, the device, in response to receiving the request, displays, viathe display device, the first user interface.

At 710, the first user interface includes, in accordance with adetermination that a relationship (e.g., a mathematical relationship; amathematical comparison) between the activity data corresponding to thefirst activity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type (e.g., the activity data (e.g., an average value of theactivity data) for the first time period reflects no change or apositive change relative to the activity data (e.g., an average value ofthe activity data) for the second time period), displaying arepresentation (e.g., 636) (e.g., a graphical or textual indication ofthe first activity metric) of the first activity metric in a firstportion (e.g., 626) of the first user interface.

At 712, the first user interface includes, in accordance with adetermination that the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a second type (e.g., the activity data for thefirst time period reflects a negative change relative to the activitydata for the second time period) (e.g., negative), displaying therepresentation (e.g., 642) (e.g., up arrow or down arrow) of the firstactivity metric in a second portion (e.g., 636) of the first userinterface different from the first portion (in some examples,representations determined to be of the first type are visually groupedwithin the user interface to be separate from representations determinedto be of the second type). Dynamically placing a representation of anactivity metric (e.g., in a first portion or a second portion of a userinterface) based on a relationship between activity data associated withthe activity metric over different time periods provides a user withvisual feedback about a current state of the activity metric and datastored on a device. For example, such placement allows a user to quicklyidentify activity metrics for which the user has a negative trendrecently. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to identify what type of data theuser needs to provide a device to change the user interface and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some examples, the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is the first type when an activity value (e.g.,average, slope of a linear fit) determined (e.g., calculated) for theactivity data corresponding to the first activity metric for the firsttime period is equal to or greater than an activity value (e.g., thesame activity value determined for the first time period) determined forthe activity data corresponding to the first activity metric for thesecond time period. In some examples, the relationship between theactivity data corresponding to the first activity metric for the firsttime period and the activity data corresponding to the first activitymetric for the second time period is the second type when the activityvalue determined for the activity data corresponding to the firstactivity metric for the first time period is less than the activityvalue determined for the activity data corresponding to the firstactivity metric for the second time period.

In some examples, the representation of the first activity metricincludes a visual indication (e.g., a graphical indication (up or downarrow); a textual indication)) (e.g., 636 b) of whether the relationshipis the first type or the second type.

In some examples, displaying the first user interface includes, inaccordance with a determination that the representation of the firstactivity metric is displayed in the first portion of the first userinterface, animating the visual indication at a first time point (e.g.,immediately on display, 0.5 seconds after display) after initiallydisplaying the first user interface (e.g., automatically upon display ofthe first user interface). In some examples, displaying the first userinterface includes, in accordance with a determination that therepresentation of the first activity metric is displayed in the secondportion of the first user interface, animating the visual indication ata second time point (e.g., 1 second, a time point selected to be afterthe completion of the animation based on the first time point) afterinitially displaying the first user interface that is after the firsttime point. Animating visual indications (associated with activitymetrics) such that visual indications associated with a first portion ofa user interface are animated after visual indications associated with asecond portion of the user interface (thereby highlighting such visualindications associated with the first behavior) provides a user withvisual feedback about a current state of the activity metrics. Forexample, animating in such a way allows a user to quickly identifyactivity metrics for which the user has a negative trend recently.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to identify what type of data the user needs toprovide a device to change the user interface and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, displaying the first user interface includes, inaccordance with a determination that the activity data corresponding tothe first activity metric meets a first set of data insufficiencycriteria (e.g., data is not available for the first time period and/orthe second time period) that includes a criterion that is met when thefirst activity metric is a first metric type (e.g., a metric that isinfrequently provided for a percentage of users; a metric that is notdirectly measured by one or more sensors of the electronic device) and acriterion that is met when the first the activity data corresponding tothe first activity metric is below a data sufficiency threshold (e.g.,data for the first and/or second time period does not exist or exists,but does not meet a threshold amount requirement), forgoing display ofthe representation of the first activity metric in the first userinterface (e.g., in the first portion and the second portion) (e.g.,irrespective of a relationship between the activity data correspondingto the first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod is a first type).

In some examples, displaying the first user interface includes, inaccordance with a determination that the activity data corresponding tothe first activity metric meets a second set of data insufficiencycriteria (e.g., data is not available for the first time period and/orthe second time period) that includes a criterion that is met when thefirst activity metric is a second metric type (e.g., a metric that isfrequently provided for a percentage of users; a metric that is directlymeasured by one or more sensors of the electronic device) and acriterion that is met when the activity data corresponding to the firstactivity metric is below the data sufficiency threshold (e.g., data forthe first and/or second time period does not exist or exists, but doesnot meet a threshold amount requirement), displaying the representationof the first activity metric in a third portion (e.g., 618 or in aposition in 612 as depicted in FIG. 6E other than positive trend portion632 and negative trend portion 638)) of the user interface that isdifferent from the first portion and the second portion with anindication (e.g., a graphical indication, a textual indication) that theactivity data corresponding to the first activity metric is insufficient(e.g., irrespective of a relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is a first type). Providing indications of whether asufficient amount of data has been received for a particular activitymetric provides a user with visual feedback about a current state ofactivity data stored on a device. Providing improved visual feedback tothe user enhances the operability of the device and makes theuser-device interface more efficient (e.g., by helping the user toidentify what type of data the user needs to provide a device to changethe user interface and reducing user mistakes when operating/interactingwith the device) which, additionally, reduces power usage and improvesbattery life of the device by enabling the user to use the device morequickly and efficiently.

In some examples, displaying the representation of the first activitymetric in a third portion of the user interface includes displaying anindication of a predicted length of time remaining for the firstactivity data corresponding to the first activity metric to meet thedata sufficiency threshold (e.g., 616) (in some examples, the predictedlength of time is based on an assumption that a sufficient amount ofactivity data for the second activity metric will be received for thelength of time). Indicating a predicted length of time needed to displaya particular activity metric provides a user with visual feedback abouta current state of activity data stored on a device and an indicationregarding how the user needs to use the device in the future to beprovided particular metrics. Providing improved visual feedback to theuser enhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to identify whattype of data the user needs to provide a device to change the userinterface and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some examples, the first time period is a first predetermined periodof time (e.g., the previous 90 days) prior to the current time (e.g.,selected based on the current time (e.g., current day/date)). In someexamples, the second time period is a second predetermined period oftime (e.g., the previous 365 days) prior to the current time that isdifferent from the first predetermined time period.

In some examples, displaying the representation of the first activitymetric in a second portion (e.g., 642) of the first user interfaceincludes displaying a first coaching indication (e.g., 642 e) (e.g.,“Let's get to walking 1 more mile per day”) including a predictioncorresponding to when (e.g., a period of time (e.g., 1 day, 5 days, 2weeks) the relationship will transition from being of the second type(e.g., negative) to being of the first type (e.g., even or positivetrend) while maintaining a future level (e.g., a predicted future level)of activity (e.g., 10% more walking per day) for the first activitymetric. In some examples, displaying the representation of the firstactivity metric in a first portion of the first user interface includesforgoing display of the first coaching indication (in some examples, therepresentation displayed in the first portion includes a second coachingindication (e.g., “keep it up!”), different than the first coachingindication). Selectively providing a prediction regarding a user'sactivity level assists the user in performing a technical task ofproviding additional activity data, thereby providing the user withvisual feedback about a current state of activity data stored on adevice. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to identify what type of data theuser needs to provide a device to change the user interface and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some examples, the electronic device includes a sensor device (e.g.,an accelerometer, a GPS, a heart rate monitor). In such examples, theactivity data corresponding to the first activity metric includesactivity data received (e.g., detected) via the sensor device.

In some examples, the activity data corresponding to the first activitymetric includes activity data received from a second electronic device(e.g., an external electronic device).

At 714, the device receives activity data corresponding to a thirdactivity metric (e.g., data corresponding to a measured level ofactivity for a user of the electronic device (e.g., data for activityperformed by the user while wearing the electronic device)) for thefirst time period (e.g., 3 months).

At 716, the device receives activity data corresponding to the thirdactivity metric for the second time period (e.g., 1 year).

At 718, displaying the first user interface includes, in accordance witha determination that a relationship (e.g., a mathematical relationship;a mathematical comparison) between the activity data corresponding tothe third activity metric for the first time period and the activitydata corresponding to the third activity metric for the second timeperiod is the first type (e.g., no change or positive), displaying arepresentation (e.g., a graphical or textual indication of the firstactivity metric) of the third activity metric in the first portion ofthe first user interface.

At 720, displaying the first user interface includes, in accordance witha determination that the relationship between the activity datacorresponding to the third activity metric for the first time period andthe activity data corresponding to the third activity metric for thesecond time period is the second type (e.g., negative), displaying arepresentation (e.g., up arrow or down arrow) of the third activitymetric in the second portion of the first user interface.

In some examples, the representation of the first activity metricincludes an indication in a first unit of measurement (e.g., calories,steps). In such examples, the representation of the third activitymetric includes an indication in a second unit of measurement (e.g.,minutes, miles) that is different than the first unit of measurement.

In some examples, the first time period (e.g., preceding 90 days) is asubset of the second time period (e.g., preceding 365 days).

In some examples, the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period includes a comparison of an average of the activitydata corresponding to the first activity metric for the first timeperiod with an average of the activity data corresponding to the firstactivity metric for the second time period.

In some examples, the activity data corresponding to the first activitymetric for the first time period is selected from a group consisting ofone or more of: a number of calories burned, an amount of time for whicha user has been detected exercising, a number of hours for which a userhas been detected to be standing for at least one minute, an amount oftime for which a user has moved, an amount of time for which a user hasstood, a walking speed, an identified fitness level for a given time fora user, a number of flights of stairs climbed, a distanced walked, and adetermined workout intensity for a user.

In some examples, the device displays a user interface with all positive(e.g., FIG. 6G) or all negative trends (e.g., FIG. 6D), where a userinterface with all positive trends is different from a user interfacewith all negative trends and a user interface with a mix of positive andnegative trends (e.g., FIG. 6E), and where a user interface with allnegative trends is different from a user interface with a mix ofpositive and negative trends. In some examples, the order of trendrepresentations is consistent between different views (e.g., allpositive, all negative, or different combinations of mixes of positivesand negatives). For example, in FIG. 6D, it can be seen that the orderis move, exercise, stand, move minutes, and walk speed. Then, in FIG.5E, while some of the representations for activity metrics havetransitioned from negative to positive, the order within positive andthe order within negative is maintained such that it keeps the order ofmove, exercise, stand, move minutes, and walk speed for each activitymetric represented in each portion (e.g., in positive, the order ismove, exercise, and move minutes, with stand missing because it is inthe second portion). In some examples, the device displays a userinterface with 10 different trends: move, exercise, stand, move minutes,stand minutes, walk speed, fitness levels, flights climbed, walkingdistance, and workout intensity. In some examples, negative trendsinclude coaching information while positive trends do not includecoaching information (e.g., 636 and 642).

Note that details of the processes described above with respect tomethod 700 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described below. For example, methods 800 and 900optionally includes one or more of the characteristics of the variousmethods described above with reference to method 700. For example,selection of an activity representation in the first user interfacedescribed in method 700 can cause display of the first user interfacedescribed in method 800. For another example, one or more coachingindications described in method 900 can be included in the first userinterface described in method 700. For brevity, these details are notrepeated below.

FIGS. 8A-8B are a flow diagram illustrating method 800 for presentingactivity trends (e.g., comparing an activity metric over two differentlengths of time) using an electronic device in accordance with someembodiments. Method 800 relates to displaying a user interface (e.g.,detailed page) with activity metric representations for a particularactivity metric, comparing a first amount of time (e.g., 90 days) with asecond amount of time (e.g., 365 days). Method 800 is performed at adevice (e.g., 100, 300, 500, 600, 664) with a display device. Someoperations in method 800 are, optionally, combined, the orders of someoperations are, optionally, changed, and some operations are,optionally, omitted.

As described below, method 800 provides an intuitive way for presentingactivity trends. The method reduces the cognitive burden on a user forpresenting activity trends, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to identify activity trends faster and more efficientlyconserves power and increases the time between battery charges.

At 802, the device (e.g., 600) receives activity data corresponding to afirst activity metric (e.g., data corresponding to a measured level ofactivity for a user of the electronic device (e.g., data for activityperformed by the user while wearing the electronic device)) for a firsttime period (e.g., 3 months).

At 804, the device receives activity data corresponding to the firstactivity metric for a second time period (e.g., 1 year), wherein thefirst time period is a subset of the second time period (e.g., thesecond time period includes the first time period). In some examples, atleast some of the activity data is detected by a sensor of theelectronic device. For example, the device includes a sensor device(e.g., an accelerometer, a GPS, a heart rate monitor) and the activitydata corresponding to the first activity metric includes activity datareceived (e.g., detected) via the sensor device. In some examples, theactivity data is received from a second electronic device. For example,the activity data corresponding to the first activity metric includesactivity data received from a second electronic device (e.g., anexternal electronic device).

At 806, the device receives a request to display a first user interface(e.g., user interface with details for a specific activity metric)(e.g., 649).

At 808, the device, in response to receiving the request, displays, viathe display device, the first user interface (e.g., 652).

At 810, the first user interface includes a representation (e.g., barsin 658 that are right of 658 c) (e.g., a graphical or textualrepresentation of a numerical value) (in some examples, therepresentation is a bar graph showing user activity data for theparticular activity metric on each day within the first time period) ofthe activity data corresponding to the first activity metric for thefirst time period.

At 812, the first user interface includes a representation (e.g., barsin 658 that are left of 658 c) (e.g., a graphical or textualrepresentation of a numerical value) (in some examples, therepresentation is a bar graph showing user activity data for theparticular activity metric on each day within the second time period) ofthe activity data corresponding to the first activity metric for thesecond time period.

In some examples, the representation of the activity data correspondingto the first activity metric for the first time period is visuallydistinct (e.g., includes a visual characteristic (e.g., a color, aborder, a shape) that is not present in the representation for thesecond time period or lacks a visual characteristic that is present inthe representation for the second time period) from the representationof the activity data corresponding to the first activity metric for thesecond time period.

At 814, the first user interface includes a representation (e.g., 656 a,656 b, 656 d, 656 e, 658 a) (e.g., a graphical or textual representationof a numerical value) of a comparison (e.g., a mathematical comparison)of the activity data corresponding to the first activity metric for thefirst time period and the activity data corresponding to the firstactivity metric for the second time period. Displaying representationsregarding different activity metrics with a comparison of activity dataover different time periods provides a user with visual feedback about acurrent state of activity data stored on a device. Providing improvedvisual feedback to the user enhances the operability of the device andmakes the user-device interface more efficient (e.g., by helping theuser to identify what type of data the user needs to provide a device tochange the user interface and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, at 816, displaying the first user interface includesdisplaying an indication (e.g., 658 a) (e.g., a textual or graphicalindication) for an average of the activity data corresponding to thefirst activity metric for the first time period. In such an example, at818, displaying the first user interface includes displaying anindication (e.g., 658 b) (e.g., a textual or graphical indication) foran average of the activity data corresponding to the first activitymetric for the second time period.

In some examples, the representation of the activity data correspondingto the first activity metric for the first time period is divided into afirst number of representations (e.g., a number of representationscorresponding to a unit (e.g., days) of the time period). In such anexample, the representation of the activity data corresponding to thefirst activity metric for the second time period is divided into asecond number of representations different from the first number ofrepresentations.

In some examples, the representation of the comparison indicates adifference between the activity data (e.g., a difference between anactivity value (e.g., average, slope of a linear fit) determined (e.g.,calculated) for the first and second time periods for the activity data)corresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period (in some examples, the representation of thecomparison indicates a difference only when the activity data for thefirst time period is less than the activity data for the second timeperiod).

In some examples, at 820, displaying the first user interface includesdisplaying a plurality of first-time-period representations for thefirst time period (e.g., empty bars in 660) (e.g., bars in a graph foreach day of the week corresponding to 90 day period), wherein: a firstfirst-time-period representation (e.g., Monday bar for 90 day period)corresponds to a length of time (e.g., a day), a secondfirst-time-period representation (e.g., Tuesday bar for 90 day period)corresponds to the length of time, the first first-time-periodrepresentation corresponds to a third time period (e.g., each Mondaywithin the 90 day period) within the first time period, and the secondfirst-time-period representation corresponds to a fourth time period(e.g., each Tuesday within the 90 day period) within the first timeperiod. In such an example, at 822, displaying the first user interfaceincludes displaying a plurality of second-time-period representationsfor the second time period (e.g., bars with diagonal lines in 660)(e.g., bars in a graph for each day of the week corresponding to 365 dayperiod), wherein: a first second-time-period representation (e.g.,Monday bar for 365 day period) corresponds to the length of time, asecond second-time-period representation (e.g., Tuesday bar for 365 dayperiod) corresponds to the length of time, the first second-time-periodrepresentation corresponds to a fifth time period (e.g., each Mondaywithin the 365 day period) within the second time period, the secondsecond-time-period representation corresponds to a sixth time period(e.g., each Tuesday within the 365 day period) within the second timeperiod, the third time period corresponds to the fifth time period(e.g., both are Mondays within their respective time periods), thefourth time period corresponds to the sixth time period (e.g., both areTuesdays within their respective time periods), the firstfirst-time-period representation is visually paired with (e.g.,displayed adjacent to (e.g., without any other interveningrepresentations)) the first second-time-period representation, and thesecond first-time-period representation is visually paired with thesecond second-time-period representation. Visually depicting a user'sactivity over time using a comparison of two different time periodsprovides a user with visual feedback about a current state of activitydata stored on a device and information regarding how the user uses thedevice over time. Providing improved visual feedback to the userenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to identify whattype of data the user needs to provide a device to change the userinterface and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some examples, at 824, displaying the first user interface includesdisplaying a representation (e.g., 662 a) of a percentage of timeperiods of a particular length (e.g., a day) of the activity datacorresponding to the first activity metric (e.g., calories burned) forthe first time period for which (e.g., during which) the first activitymetric met a threshold activity level (e.g., 500 calories/day) (in someexamples, the user interface includes a percentage of days during a 90day period in which the value of a activity metric (e.g., caloriesburned) met a threshold value (e.g., 85% of the days logged a caloriesburned metric of greater than 500 calories). Linking an activity metricwith a particular threshold and tracking a user's past ability to meetthe threshold provides a user with visual feedback about how the useruses the device. Providing improved visual feedback to the user enhancesthe operability of the device and makes the user-device interface moreefficient (e.g., by helping the user to identify what type of data theuser needs to provide a device to change the user interface and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some examples, at 824, displaying the first user interface includesdisplaying an icon (e.g., 656 b) indicating whether a relationship(e.g., a mathematical relationship; a mathematical comparison) betweenthe activity data corresponding to the first activity metric for thefirst time period and the activity data corresponding to the firstactivity metric for the second time period is a first type (e.g., theactivity data (e.g., an average value of the activity data) for thefirst time period reflects no change or a positive change relative tothe activity data (e.g., an average value of the activity data) for thesecond time period) or a second type (e.g., the activity data for thefirst time period reflects a negative change relative to the activitydata for the second time period).

Note that details of the processes described above with respect tomethod 800 (e.g., FIGS. 8A-8B) are also applicable in an analogousmanner to the methods described below. For example, methods 700 and 900optionally includes one or more of the characteristics of the variousmethods described above and below with reference to method 800. Forexample, selection of a back affordance in the first user interfacedescribed in method 900 can cause display of the first user interfacedescribed in method 700. For another example, one or more coachingindications described in method 900 can be included in the first userinterface described in method 800. For brevity, these details are notrepeated below.

FIG. 9 is a flow diagram illustrating method 900 for presenting activitytrends (e.g., providing different coaching depending on relationshipbetween data of time periods; coaching includes a prediction of whenrelationship will change, if certain activity level is maintained) usingan electronic device in accordance with some embodiments. Method 900 isperformed at a device (e.g., 100, 300, 500, 600, 664) with a displaydevice. Some operations in method 900 are, optionally, combined, theorders of some operations are, optionally, changed, and some operationsare, optionally, omitted.

As described below, method 900 provides an intuitive way for presentingactivity trends. The method reduces the cognitive burden on a user forpresenting activity trends, thereby creating a more efficienthuman-machine interface. For battery-operated computing devices,enabling a user to identify activity trends faster and more efficientlyconserves power and increases the time between battery charges.

At 902, the device (e.g., 600) receives activity data corresponding to afirst activity metric (e.g., data corresponding to a measured level ofactivity for a user of the electronic device (e.g., data for activityperformed by the user while wearing the electronic device)) for a firsttime period (e.g., 3 months).

At 904, the device receives activity data corresponding to the firstactivity metric for a second time period (e.g., 1 year), different thanthe first period of time.

At 906, the device receives a request (e.g., 607, 611, 649) to display afirst user interface (e.g., 612, 652) (e.g., user interface thatincludes comparisons of activity data for a plurality of activitymetrics or user interface with details for a specific activity metric).

At 908, the device, in response to receiving the request, displays, viathe display device, the first user interface, the first user interfaceincluding a representation (e.g., 642, or 656) (e.g., a graphical ortextual indication of the first activity metric) of the first activitymetric.

At 910, the representation of the first activity metric includes, inaccordance with a determination that a relationship (e.g., amathematical relationship; a mathematical comparison) between theactivity data corresponding to the first activity metric for the firsttime period and the activity data corresponding to the first activitymetric for the second time period is a first type (e.g., negative trendfor which can be remedied within 1 day), displaying a first coachingindication (e.g., 628 e) (e.g., “Don't forget to stand for one minuteper hour throughout the day”) including a prediction (e.g., “the day”the 628) corresponding to when (e.g., a period of time (e.g., 1 day, 5days, 2 weeks) the relationship will transition from being of the firsttype to being of a second type (e.g., even or positive trend), differentfrom the first type, while maintaining a future level of activity (e.g.,10% more walking per day) for the first activity metric.

At 912, the representation of the first activity metric includes, inaccordance with a determination that the relationship is a third type(e.g., negative trend for which can be remedied more than a week butwithin 1 month) different from the first type, a second coachingindication (e.g., 624 e) (e.g., “Try to move around for 10 extraminutes”) that does not include a prediction corresponding to when(e.g., a period of time (e.g., 1 day, 5 days, 2 weeks) the relationshipwill transition from being of the third type to being of the secondtype. Dynamically modifying activity-related information provided to auser based on classifying the user's activity provides a user withvisual feedback about a current state of activity data stored on adevice. Providing improved visual feedback to the user enhances theoperability of the device and makes the user-device interface moreefficient (e.g., by helping the user to identify what type of data theuser needs to provide a device to change the user interface and reducinguser mistakes when operating/interacting with the device) which,additionally, reduces power usage and improves battery life of thedevice by enabling the user to use the device more quickly andefficiently.

In some examples, the first type requires that the relationship betweenthe activity data (e.g., relationship between an activity value (e.g.,average, slope of a linear fit) determined (e.g., calculated) for theactivity data corresponding to the first activity metric for the firsttime period and the second time period)) corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isnegative (e.g., the average value for the first time period is 50calories burned/day and the average value for the second time period is75 calories burned/day with a difference in the values being −25calories burned/day)).

In some examples, the representation of the first activity metricincludes: while the relationship between the activity data correspondingto the first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod is the first type (this in accordance means that the trend isnegative): in accordance with a determination that a relationshipbetween the activity data corresponding to the first activity metric forthe second time period and the activity data corresponding to the firstactivity metric for a subset of the first time period (e.g., the last 7days in a 90 day period) is a fourth type (e.g., recently positive),displaying a third coaching indication (e.g., “You have been improvinglately, but let's get to walking 1 more mile per day to reach youryearly average”; a coaching indication in addition to the first coachingindication), and in accordance with a determination that a relationshipbetween the activity data corresponding to the first activity metric forthe second time period and the activity data corresponding to the firstactivity metric for the subset of the first time period (e.g., the last7 days in a 90 day period) is a fifth type (e.g., recently negative),displaying a fourth coaching indication that is different from the thirdcoaching indication (e.g., “let's get to walking 1 more mile per day toreach your yearly average”). Dynamically modifying activity-relatedinformation provided to a user based on a user's recent behavior ascompared to less recent behavior provides a user with visual feedbackabout a recent state of activity data stored on a device. Providingimproved visual feedback to the user enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to identify what type of data the user needs to providea device to change the user interface and reducing user mistakes whenoperating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, the representation of the first activity metricincludes: while the relationship between the activity data correspondingto the first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod is the first type: in accordance with a determination that theprediction exceeds a first time threshold (e.g., >1 day) and is lessthan a second time threshold (e.g., <7 days), displaying a fifthcoaching indication (e.g., a coaching indication in addition to thefirst coaching indication), and in accordance with a determination thatthe prediction exceeds the second time threshold (e.g., >7 days),displaying a sixth coaching indication (e.g., a coaching indication inaddition to the first coaching indication) that is different from thefifth coaching indication. Dynamically modifying activity-relatedinformation provided to a user based on a link of time predicted for theactivity data to be similar to the past provides a user with visualfeedback about a current state of activity data stored on a device.Providing improved visual feedback to the user enhances the operabilityof the device and makes the user-device interface more efficient (e.g.,by helping the user to identify what type of data the user needs toprovide a device to change the user interface and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, at 914, the device, while the relationship between theactivity data corresponding to the first activity metric for the firsttime period and the activity data corresponding to the first activitymetric for the second time period is the first type (this in accordancemeans that the trend is negative): in accordance with a determinationthat the prediction is a first classification (e.g., requiring a levelof activity that exceeds threshold (e.g., an unreasonably highrequirement)), displaying a fifth coaching indication (e.g., “Dobetter”) without a prediction corresponding to when the relationshipbetween the activity data corresponding to the first activity metric forthe first time period and the activity data corresponding to the firstactivity metric for the second time period will be of the second type(e.g., even or positive trend) while maintaining the future level ofactivity (e.g., 10% more walking per day) for the first activity metric.

In some examples, the prediction is determined by: removing old datafrom the activity data corresponding to the first activity metric forthe first time period, removing old data from the activity datacorresponding to the first activity metric for the second time period,and until the relationship between the activity data corresponding tothe first activity metric for the first time period and the activitydata corresponding to the first activity metric for the second timeperiod is the second type, adding predicted data to the activity datacorresponding to the first activity metric for the first time period,and adding the old data from the activity data corresponding to thefirst activity metric for the first time period to the activity datacorresponding to the first activity metric for the second time period(in some examples, trend reverses in 1 day, which only requires takingthe last actual 89/364 days of data and adding one predicted day).

Note that details of the processes described above with respect tomethod 900 (e.g., FIG. 9 ) are also applicable in an analogous manner tothe methods described below. For example, methods 700 and 800 optionallyincludes one or more of the characteristics of the various methodsdescribed above with reference to method 900.

FIGS. 10A-10N illustrate exemplary user interfaces for managingworkouts, in accordance with some embodiments. The user interfaces inthese figures are used to illustrate the processes described below,including the processes in FIGS. 11A-11B.

FIG. 10A depicts electronic device 1000 displaying watch face userinterface 1004 via display device 1002. Electronic device 1000 includesvarious input mechanisms that receive user input, such as rotatableinput mechanism 1001, which is able to receive a rotatable input (and,in some examples, can also receive a push input). In some examples,electronic device 1000 includes one or more features of devices 100,300, or 500. Watch face user interface 604 includes workout affordance1006 for initiating a workout application (e.g., an application to trackworkouts performed by a user associated with electronic device 1000).

Referring to FIG. 10A, electronic device 1000 receives user input 1007corresponding to selection of workout affordance 1006. User input 1007can include a touch gesture, such as a tap gesture on workout affordance1006, causing the workout application to be initiated (e.g., display ofa user interface of the workout application, such as workout platteruser interface 1008 as depicted in FIG. 10B).

FIG. 10B depicts electronic device 1000 displaying workout platter userinterface 1008 via display device 1002. Workout platter user interface1008 includes scrollable list of affordances 1010, which are eachassociated with a respective physical activity tracking function for aphysical activity. For example, scrollable list of affordances 1010includes walk affordance 1012 a, which corresponds to a physicalactivity tracking function for an outdoor walk.

It is noted that scrollable list of affordances 1010 includes additionalaffordances corresponding to other physical activity tracking functionsthat are not currently displayed but can be displayed in response to ascrolling input (e.g., rotation of rotational mechanism 1001). In someembodiments, scrollable list of affordances 1010 includes more workoutsaffordance, which will be described in further detail below (see atleast FIG. 10F).

Referring to FIG. 10B, electronic device 1000 receives user input 1013corresponding to selection of walk affordance 1012 a. User input 1013can include a touch gesture, such as a tap gesture on walk affordance1012 a, causing a physical activity tracking function associated withwalk affordance 1012 a to be launched (e.g., display of one or more userinterfaces of the workout application, with a final user interfacecorresponding to the physical activity tracking function associated withwalk affordance 1012 a (e.g., walk user interface 1014 as depicted inFIG. 10C).

FIG. 10C depicts electronic device 1000 displaying walk user interface1014 via display device 1002. Walk user interface 1014 displays a set oftracked metrics (e.g., “00:01.40,” “0 active cal,” “70 BPM,” “15′11”average mile,” and “0 ft”) (which are tracked by the physical activitytracking function associated with walk affordance 1012 a.

In some examples, tracking of the set of tracked metrics is performed byone or more tracking sensors of electronic device 1000. For example,electronic device 1000 tracks physical activity via tracking sensors (orworkout sensors) that communicate with workout support module 142 (asdepicted in FIG. 3 ).

Referring to FIG. 10C, electronic device 1000 receives user input 1015corresponding to a swipe gesture. User input 1015 can include a touchgesture, causing a control user interface of the workout application tobe displayed (e.g., control user interface 1016 as depicted in FIG.10D).

FIG. 10D depicts electronic device 1000 displaying control userinterface 1016 via display device 1002. In some examples, device 1000displays control user interface 1016 in response to a user input (e.g.,user input 1015) while displaying walk user interface 1014. Control userinterface 1016 includes affordances to control various functionalitiesof the workout application. For example, control user interface 1016includes end workout affordance 1018 (configured to, when selected, enda currently running workout).

Referring to FIG. 10D, electronic device 1000 receives user input 1019corresponding to selection of end workout affordance 1018. User input1019 can include a touch gesture, such as a tap gesture on end workoutaffordance 1018, causing the currently running workout (associated withoutdoor walk) to end and workout platter user interface 1008 to bedisplayed, as depicted in FIG. 10E.

FIG. 10E depicts electronic device 1000 displaying, once again, workoutplatter user interface 1008 via display device 1002 and performing ascrolling operation. For example, rotational input 1021 is received atrotatable input mechanism 1001. In response to rotational input 1021, asdepicted in FIG. 10F, scrollable list of affordances 1010 is scrolled inan upward direction such that more workouts affordance 1022 aredisplayed.

Referring to FIG. 10F, electronic device 1000 receives user input 1023corresponding to selection of more workouts affordance 1022. User input1023 can include a touch gesture, such as a tap gesture on more workoutsaffordance 1022, causing a user interface with a list of availableworkouts to be displayed (e.g., workout list user interface 1024 asdepicted in 10G).

FIG. 10G depicts electronic device 1000 displaying workout list userinterface 1024 via display device 1002. In some examples, workout listuser interface 1024 includes a scrollable list of affordances withpopular portion 1026 (as depicted in FIG. 10G) and alphabetical portion1027 (as depicted in FIG. 10H).

Referring to FIG. 10G, popular portion 1026 includes multiple workoutaffordances, each workout affordance determined to be most relevant(e.g., popular among users, most frequently used by a user associatedwith electronic device 1000, etc.). For example, the multiple workoutaffordances in popular portion 1026 includes dance affordance 1028.Selection of a particular workout affordance of the multiple workoutaffordances causes (1) a workout affordance corresponding to theparticular workout affordance to be added to workout platter userinterface 1008 such that the workout affordance can be selected in thefuture when a user navigates to workout platter user interface 1008and/or (2) a physical activity tracking function corresponding to theworkout affordance to be launched.

Referring to FIG. 10H, alphabetical portion 1027 includes a list ofworkout affordances in alphabetical order, including AUS footballaffordance 1030 (e.g., an affordance corresponding to function fortracking activity associated with Australian rules football). It shouldbe recognized that the list of workout affordances can be ordered in adifferent manner. Similar to popular portion 1026, selection of aparticular workout affordance in the list of workout affordances causes(1) a workout affordance corresponding to the particular workoutaffordance to be added to workout platter user interface 1008 such thatthe workout affordance can be selected in the future when a usernavigates to workout platter user interface 1008 and/or (2) a physicalactivity tracking function corresponding to the workout affordance to belaunched.

Similar to as described above for FIG. 10E, FIG. 10F depicts electronicdevice 1000 receiving rotational input 1029 at rotatable input mechanism1001. In response to rotational input 1029, the scrollable list ofaffordances of workout list user interface 1024 is scrolled in an upwarddirection such that more workout affordances are displayed (e.g., otherworkout affordances in popular portion 1026 (not depicted) or workoutaffordances in alphabetical portion 1021 (as depicted in FIG. 10H)).

FIG. 10H depicts electronic device 1000 receiving user input 1031corresponding to selection of AUS football affordance 1030. User input1031 can include a touch gesture, such as a tap gesture on AUS footballaffordance 1030, causing a workout affordance corresponding to AUSfootball affordance 1030 to be added to workout platter user interface1008 (e.g., AUS football affordance 1034 as depicted in FIG. 101 ).

Similar as described above for FIGS. 10B-10D, FIGS. 101-10K depict userinterfaces involved in beginning and ending a workout. For example, FIG.101 depicts electronic device 1000 displaying workout platter userinterface 1008 via display device 1002. Workout platter user interface1008 depicted in FIG. 101 includes AUS football affordance 1034, showingthat workout platter user interface 1008 depicted in FIG. 101 is in astate after AUS football affordance 1034 has been added to workoutplatter user interface 1008 (e.g., after FIG. 10H) (see FIG. 10F, whichdoes not include AUS football affordance 1034). AUS football affordance1034 corresponds to a physical activity tracking function for Australianfootball.

Referring to FIG. 101 , electronic device 1000 receives user input 1035corresponding to selection of AUS football affordance 1034. User input1035 can include a touch gesture, such as a tap gesture on AUS footballaffordance 1034, causing a physical activity tracking functionassociated with AUS football affordance 1034 to be launched (e.g.,display of one or more user interfaces of the workout application, witha final user interface corresponding to the physical activity trackingfunction associated with AUS football affordance 1034 (e.g., AUSfootball user interface 1036 as depicted in FIG. 10J).

FIG. 10J depicts electronic device 1000 displaying AUS footballinterface 1036 via display device 1002. AUS football interface 1036displays a set of tracked metrics (e.g., “00.01.29,” “0 active cal,” “0total cal,” and “—BPM”) (which are tracked by the physical activitytracking function associated with AUS football affordance 1034).

In some examples, tracking of the set of tracked metrics is performed byone or more tracking sensors of electronic device 1000. For example,electronic device 1000 tracks physical activity via tracking sensors (orworkout sensors) that communicate with workout support module 142 (asdepicted in FIG. 3 ).

Referring to FIG. 10J, electronic device 1000 receives user input 1037corresponding to a swipe gesture. User input 1037 can include a touchgesture, causing a control user interface of the workout application tobe displayed (e.g., control user interface 1038 as depicted in FIG.10K).

FIG. 10K depicts electronic device 1000 displaying control userinterface 1038 via display device 1002. Control user interface 1038includes affordances to control various functionalities of the workoutapplication. For example, control user interface 1038 includes endworkout affordance 1040 (configured to, when selected, end a currentlyrunning workout).

Referring to FIG. 10K, electronic device 1000 receives user input 1041corresponding to selection of end workout affordance 1040. User input1041 can include a touch gesture, such as a tap gesture on end workoutaffordance 1040, causing the currently running workout (associated withAustralian football) to end and workout platter user interface 1008 tobe displayed, as depicted in FIG. 10L.

FIG. 10L depicts electronic device 1000 displaying workout platter userinterface 1008 via display device 1002. Workout platter user interface1008 depicted in FIG. 10L includes AUS football affordance 1034, showingthat workout platter user interface 1008 depicted in FIG. 10L is in astate after AUS football affordance 1034 has been added to workoutplatter user interface 1008 (e.g., after FIG. 10H) (see FIG. 10F, whichdoes not include AUS football affordance 1034).

Referring to FIG. 10L, electronic device 1000 receives user input 1043corresponding to a swipe gesture associated with (e.g., at leastpartially on top of) AUS football affordance 1034. User input 1043 caninclude a touch gesture, causing (1) AUS football affordance 1034 tomove to the left and (2) delete affordance 1044 to be displayed in aposition that was at least partially previously occupied by AUS footballaffordance 1034 prior to moving (as depicted in FIG. 10M).

FIG. 10M depicts electronic device 1000 displaying workout platter userinterface 1008 via display device 1002 with AUS football affordance 1034moved to the left and delete affordance 1044 displayed in a locationthat was at least partially covered up by AUS football affordance 1034prior to being moved to the left. Referring to FIG. 10L, electronicdevice 1000 receives user input 1045 corresponding to selection ofdelete affordance 1040. User input 1041 can include a touch gesture,such as a tap gesture on end workout affordance 1044, causing AUSfootball affordance 1034 to be removed from workout platter userinterface 1008 (as depicted in FIG. 10N) until AUS football affordance1034 is added again using the process described in FIGS. 10F-10H. FIG.10N depicts electronic device 1000 displaying workout platter userinterface 1008 via display device 1002 without AUS football affordance1034.

FIGS. 11A-11B are a flow diagram illustrating method 1100 for managingworkouts (e.g., more-workouts option for workout platters, allowing userto view a list of workouts to add to workout platters) using anelectronic device in accordance with some embodiments. Method 1100 isperformed at a device (e.g., 100, 300, 500, 600, 664, 1000) with adisplay device. Some operations in method 1100 are, optionally,combined, the orders of some operations are, optionally, changed, andsome operations are, optionally, omitted.

As described below, method 1100 provides an intuitive way for managingworkouts. The method reduces the cognitive burden on a user for managingworkouts, thereby creating a more efficient human-machine interface. Forbattery-operated computing devices, enabling a user to add and deleteworkout affordances associated with physical activity tracking functionsfaster and more efficiently conserves power and increases the timebetween battery charges.

At 1102, the device (e.g., 1000) displays, via the display device, afirst instance of a first user interface (e.g., 1008 as depicted inFIGS. 10B, 10E, and 10F) including a first set of affordances (e.g.,1012 a, 1012 b) (e.g., workout platters) associated with physicalactivity tracking functions (in some examples, different affordances ina plurality of the scrollable list of affordances correspond todifferent physical activities), wherein the first set of affordancesincludes a first affordance (e.g., 1012 a) associated with a firstphysical activity tracking function.

At 1104, while displaying the first instance of the first userinterface, the device receives a user input (e.g., 1013) (e.g., a tap inthe user interface).

At 1106, in response to receiving the user input, in accordance with adetermination that the user input is detected at the first affordance(e.g., run option) in the first set of affordances, the device launches(e.g., activating, starting) the first physical activity trackingfunction (e.g., 1014) (e.g., running).

At 1108, in further response to receiving the user input, in accordancewith a determination that the user input is detected at a secondaffordance (e.g., 1022) (e.g., more-workouts option) in the first set ofaffordances, the device displays a second user interface (e.g., 1024)(e.g., more-workouts interface) that includes a third affordance (e.g.,1030) associated with a second physical activity tracking function(e.g., walking option).

At 1110, the device receives a set of one or more inputs (e.g., 1031),the set of one or more inputs including an input corresponding toselection of the third affordance.

At 1112, in response to receiving the set of one or more inputs, thedevice displays a second instance (e.g., 1008 as depicted in FIG. 101 )of first user interface, wherein: the second instance of the first userinterface includes the first affordance and a fourth affordance (e.g.,1034) associated with the second physical activity tracking function(e.g., an affordance that, when selected, launches the second physicalactivity tracking function), and the first instance of the first userinterface does not include an affordance (e.g., any affordance)associated with the second physical activity tracking function. Updatinga list of physical activity tracking functions shown to a user on aninitial user interface provides the user with more control of the deviceby helping the user avoid unintentionally executing physical activitytracking functions and simultaneously reducing the number of steps thata user must take to reach desired physical activity tracking functions.Providing additional control of the device without cluttering the UIwith additional displayed controls enhances the operability of thedevice and makes the user-device interface more efficient (e.g., byhelping the user to provide proper inputs and reducing user mistakeswhen operating/interacting with the device) which, additionally, reducespower usage and improves battery life of the device by enabling the userto use the device more quickly and efficiently.

In some examples, the first set of affordances includes a fifthaffordance (e.g., 1012 b) associated with a third physical activitytracking function (e.g., golfing option) different from the firstphysical activity tracking function and the second physical activitytracking function.

In some examples, the input corresponding to selection of the thirdaffordance causes the second instance of the first user interface to bedisplayed (in some examples, the input corresponding to selection of thethird affordance is the terminal input (e.g., the only input) in the setof one or more inputs).

In some examples, the second instance of the first user interfaceincludes the second affordance.

In some examples, at 1114, the device receives an input (e.g., 1031)corresponding to selection of the second affordance within the secondinstance of the first user interface.

In some examples, at 1116, in response to receiving the inputcorresponding to selection of the second affordance within the secondinstance of the first user interface, the device displays a secondinstance of the second user interface (e.g., 1024) (e.g., more-workoutsinterface) that does not include an affordance associated with thesecond physical activity tracking function.

In some examples, at 1118, while displaying the second instance of thefirst user interface, the device receives a second set of one or moreinputs, the second set of one or more inputs including an input (e.g.,1043) corresponding to the fourth affordance associated with the secondphysical activity tracking function (e.g., an affordance correspondingto an activity tracking function that was previously added to the userinterface) (e.g., a set of inputs corresponding to a request to removethe fourth affordance from the first user interface).

In some examples, in response to receiving the second set of one or moreinputs, the device displays a third instance of the first user interface(e.g., 1008 as depicted in FIG. 10N), wherein the third instance of thefirst user interface does not include an affordance associated with thesecond physical activity tracking function. Allowing a user to quicklyand efficiently remove physical activity tracking functions from a listof physical activity tracking functions provides the user with morecontrol of the device by helping the user avoid unintentionallyexecuting physical activity tracking functions and simultaneouslyreducing the number of steps that a user must take to reach desiredphysical activity tracking functions. Providing additional control ofthe device without cluttering the UI with additional displayed controlsenhances the operability of the device and makes the user-deviceinterface more efficient (e.g., by helping the user to provide properinputs and reducing user mistakes when operating/interacting with thedevice) which, additionally, reduces power usage and improves batterylife of the device by enabling the user to use the device more quicklyand efficiently.

In some examples, receiving the second set of one or more inputsincludes. receiving a swipe gesture (e.g., 1043) corresponding to thefourth affordance and a tap gesture (e.g., 1045) corresponding to adelete affordance (e.g., 1044) associated with the fourth affordance(e.g., a delete affordance that is displayed in response to receivingthe swipe gesture).

Note that details of the processes described above with respect tomethod 1100 (e.g., FIGS. 7A-7B) are also applicable in an analogousmanner to the methods described above. For example, methods 700, 800,and 900 optionally includes one or more of the characteristics of thevarious methods described above with reference to method 1100. Forexample, deletion of a representation as described in methods 700, 800,and 900 can be performed as described in method 1100.

FIGS. 12A-12F illustrate exemplary user interfaces for displayingawards, in accordance with some embodiments. FIG. 12A depicts electronicdevice 1000 displaying activity application user interface 1204 viadisplay device 1002. Activity application user interface 1204 includesactivity affordance 1206, friends affordance 1208, and awards affordance1210.

Each of these affordances are configured, when selected, to causeelectronic device 1000 to display a user interface corresponding to therespective affordance. For example, activity affordance 1206 correspondsto a user interface for displaying information related to activity of auser associated with electronic device 1000 (as depicted in FIG. 12B).Friends affordance 1208 corresponds to a user interface for managingfriends (e.g., users for which are sending data to and/or receiving datafrom the user associated with electronic device (e.g., sharing)) of theuser associated with electronic device 1000 (as depicted in FIG. 12C).Awards affordance 1210 corresponds to a user interface for displayingawards of the user associated with electronic device 1000 (as depictedin FIG. 12D).

Referring to FIG. 12A, electronic device 1000 receives user input 1207corresponding to selection of activity affordance 1206. User input 1207can include a touch gesture, such as a tap gesture on activityaffordance 1206, causing a user interface associated with activityaffordance 1206 to be displayed (e.g., activity user interface 1212).

FIG. 12B depicts electronic device 1000 displaying activity userinterface 1212 via display device 1002. Activity user interface 1212includes information related to activity of a user associated withelectronic device 1000 (e.g., three rings, which each ring representingan amount of a different activity metric that the user has completedduring a current day).

Referring to FIG. 12B, electronic device 1000 receives user input 1213corresponding to a swipe gesture. User input 1213 can include a touchgesture, causing a user interface for managing friends to be displayed(e.g., friends user interface 1216 as depicted in FIG. 12C).

FIG. 12C depicts electronic device 1000 displaying friends userinterface 1216 via display device 1002. Friends user interface 1212includes multiple affordances, each affordance corresponding to a userfor which the user associated with electronic device 1000 is sharingwith.

Referring to FIG. 12C, electronic device 1000 receives user input 1217corresponding to a swipe gesture. User input 1217 can include a touchgesture, causing a user interface for displaying awards to be displayed(e.g., awards user interface 1218 as depicted in FIG. 12D). In someexamples, the swipe gesture depicted in FIG. 12C is determined to be thesame direction as the swipe gesture depicted in FIG. 12B. In suchexamples, if a swipe gesture on friends user interface 1216 isdetermined to be the opposite direction as the swipe gesture depicted inFIG. 12B, the swipe gesture causes activity user interface 1212 to bedisplayed.

FIG. 12D depicts electronic device 1000 displaying awards user interface1218 via display device 1002. Awards user interface 1212 includesmultiple sections (e.g., 1220 a-1220 d), each section including one ormore representations of awards corresponding to the respective section.For example, recent section 1220 a includes one or more representationsof awards that were recently received by the user of electronic device1000 (e.g., representation 1222 a). For another example, March challengesection 1220 b includes one or more representations of awards that areassociated with a March challenge (e.g., representation 1222 b).

A representation of an award can include one or more visual attributesindicating that the award have been awarded to the user of electronicdevice 1000. For example, representation 1222 a can be a first set ofone or more colors while representation 1222 b can be a second set ofone or more colors, the first set of one or more colors indicating thatan award corresponding to representation 1222 a has been awarded to theuser and the second set of one or more colors indicating that an awardcorresponding to representation 1222 b has not been awarded to the user.

Referring to FIG. 12D, electronic device 1000 receives user input 1223corresponding to selection of representation 1222 b. User input 1223 caninclude a touch gesture, such as a tap gesture on representation 1222 b,causing a user interface associated with representation 1222 b to bedisplayed (e.g., 1224 or 1228).

FIG. 12E depicts electronic device 1000 displaying non-awarded detaileduser interface 1224 via display device 1002. Non-awarded detailed userinterface 1224 corresponds to representation 1222 b based on user input1223 corresponding to selection of representation 1222 b. Non-awardeddetailed user interface 1224 includes a representation of representation1222 b (e.g., representation 1226). In some examples, representation1226 is larger than representation 1222 b (not illustrated). Non-awardeddetailed user interface 1224 includes text indicating how the user canearn an award corresponding to representation 1226 (“Earn this award byexercising 1000 minutes this month”).

FIG. 12F depicts electronic device 1000 displaying awarded detailed userinterface 1228 via display device 1002. Once an award has been given tothe user, a representation corresponding to the award can change. Forexample, FIG. 12F depicts representation 1230, which corresponds torepresentation 1226 except that the appearance of representation 1230 isdifferent from representation 1226. In some examples, the differentappearance corresponds to representation 1226 being a first set of oneor more colors and representation 1230 being a second set of one or morecolors different from the first set of one or more colors, thedifference indicating that an award corresponding to representation 1230has been awarded and an award corresponding to representation 1226 hasnot been awarded.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the techniques and their practical applications. Othersskilled in the art are thereby enabled to best utilize the techniquesand various embodiments with various modifications as are suited to theparticular use contemplated.

Although the disclosure and examples have been fully described withreference to the accompanying drawings, it is to be noted that variouschanges and modifications will become apparent to those skilled in theart. Such changes and modifications are to be understood as beingincluded within the scope of the disclosure and examples as defined bythe claims.

As described above, one aspect of the present technology is thegathering and use of data available from various sources to improvetracking of activity and viewing of details related to the activity. Thepresent disclosure contemplates that in some instances, this gathereddata may include personal information data that uniquely identifies orcan be used to contact or locate a specific person. Such personalinformation data can include demographic data, location-based data,telephone numbers, email addresses, twitter IDs, home addresses, data orrecords relating to a user's health or level of fitness (e.g., vitalsigns measurements, medication information, exercise information), dateof birth, or any other identifying or personal information.

The present disclosure recognizes that the use of such personalinformation data, in the present technology, can be used to the benefitof users. For example, the personal information data can be used totrack activity and view details related to the activity. Accordingly,use of such personal information data enables improved tracking ofactivity and improved viewing of details related to the activity.Further, other uses for personal information data that benefit the userare also contemplated by the present disclosure. For instance, healthand fitness data may be used to provide insights into a user's generalwellness, or may be used as positive feedback to individuals usingtechnology to pursue wellness goals.

The present disclosure contemplates that the entities responsible forthe collection, analysis, disclosure, transfer, storage, or other use ofsuch personal information data will comply with well-established privacypolicies and/or privacy practices. In particular, such entities shouldimplement and consistently use privacy policies and practices that aregenerally recognized as meeting or exceeding industry or governmentalrequirements for maintaining personal information data private andsecure. Such policies should be easily accessible by users, and shouldbe updated as the collection and/or use of data changes. Personalinformation from users should be collected for legitimate and reasonableuses of the entity and not shared or sold outside of those legitimateuses. Further, such collection/sharing should occur after receiving theinformed consent of the users. Additionally, such entities shouldconsider taking any needed steps for safeguarding and securing access tosuch personal information data and ensuring that others with access tothe personal information data adhere to their privacy policies andprocedures. Further, such entities can subject themselves to evaluationby third parties to certify their adherence to widely accepted privacypolicies and practices. In addition, policies and practices should beadapted for the particular types of personal information data beingcollected and/or accessed and adapted to applicable laws and standards,including jurisdiction-specific considerations. For instance, in the US,collection of or access to certain health data may be governed byfederal and/or state laws, such as the Health Insurance Portability andAccountability Act (HIPAA); whereas health data in other countries maybe subject to other regulations and policies and should be handledaccordingly. Hence different privacy practices should be maintained fordifferent personal data types in each country.

Despite the foregoing, the present disclosure also contemplatesembodiments in which users selectively block the use of, or access to,personal information data. That is, the present disclosure contemplatesthat hardware and/or software elements can be provided to prevent orblock access to such personal information data. For example, in the caseof activity services, the present technology can be configured to allowusers to select to “opt in” or “opt out” of participation in thecollection of personal information data during registration for servicesor anytime thereafter. In another example, users can select not toprovide activity data for targeted activity services. In yet anotherexample, users can select to limit the length of time activity data ismaintained or entirely prohibit the development of trend data. Inaddition to providing “opt in” and “opt out” options, the presentdisclosure contemplates providing notifications relating to the accessor use of personal information. For instance, a user may be notifiedupon downloading an app that their personal information data will beaccessed and then reminded again just before personal information datais accessed by the app.

Moreover, it is the intent of the present disclosure that personalinformation data should be managed and handled in a way to minimizerisks of unintentional or unauthorized access or use. Risk can beminimized by limiting the collection of data and deleting data once itis no longer needed. In addition, and when applicable, including incertain health related applications, data de-identification can be usedto protect a user's privacy. De-identification may be facilitated, whenappropriate, by removing specific identifiers (e.g., date of birth,etc.), controlling the amount or specificity of data stored (e.g.,collecting location data a city level rather than at an address level),controlling how data is stored (e.g., aggregating data across users),and/or other methods.

Therefore, although the present disclosure broadly covers use ofpersonal information data to implement one or more various disclosedembodiments, the present disclosure also contemplates that the variousembodiments can also be implemented without the need for accessing suchpersonal information data. That is, the various embodiments of thepresent technology are not rendered inoperable due to the lack of all ora portion of such personal information data. For example, activity canbe tracked and details related to the activity viewed by inferringpreferences based on non-personal information data or a bare minimumamount of personal information, such as the content being requested bythe device associated with a user, other non-personal informationavailable to the activity services, or publicly available information.

What is claimed is:
 1. A computer system configured to communicate witha display generation component and one or more input devices,comprising: one or more processors; and memory storing one or moreprograms configured to be executed by the one or more processors, theone or more programs including instructions for: receiving: activitydata corresponding to a first activity metric for a first time period;and activity data corresponding to the first activity metric for asecond time period, different than the first time period; receiving arequest to display a first user interface; and in response to receivingthe request, displaying, via the display generation component, the firstuser interface, the first user interface including a representation ofthe first activity metric, wherein the representation of the firstactivity metric includes: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, a first coaching indication including a predictioncorresponding to when the relationship will transition from being of thefirst type to being of a second type, different from the first type,while maintaining a future level of activity for the first activitymetric; and in accordance with a determination that the relationship isa third type different from the first type, a second coaching indicationthat does not include a prediction corresponding to when therelationship will transition from being of the third type to being ofthe second type.
 2. The computer system of claim 1, wherein the firsttype requires that the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is negative.
 3. The computer system of claim 1,wherein the representation of the first activity metric includes: whilethe relationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isthe first type: in accordance with a determination that a relationshipbetween the activity data corresponding to the first activity metric forthe second time period and the activity data corresponding to the firstactivity metric for a subset of the first time period is a fourth type,displaying a third coaching indication; and in accordance with adetermination that a relationship between the activity datacorresponding to the first activity metric for the second time periodand the activity data corresponding to the first activity metric for thesubset of the first time period is a fifth type, displaying a fourthcoaching indication that is different from the third coachingindication.
 4. The computer system of claim 1, wherein therepresentation of the first activity metric includes: while therelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isthe first type: in accordance with a determination that the predictionexceeds a first time threshold and is less than a second time threshold,displaying a fifth coaching indication; and in accordance with adetermination that the prediction exceeds the second time threshold,displaying a sixth coaching indication that is different from the fifthcoaching indication.
 5. The computer system of claim 1, wherein the oneor more programs further include instructions for: while therelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isthe first type: in accordance with a determination that the predictionis a first classification, displaying a fifth coaching indicationwithout a prediction corresponding to when the relationship between theactivity data corresponding to the first activity metric for the firsttime period and the activity data corresponding to the first activitymetric for the second time period will be of the second type whilemaintaining the future level of activity for the first activity metric.6. The computer system of claim 1, wherein the prediction is determinedby: removing old data from the activity data corresponding to the firstactivity metric for the first time period, removing old data from theactivity data corresponding to the first activity metric for the secondtime period, and until the relationship between the activity datacorresponding to the first activity metric for the first time period andthe activity data corresponding to the first activity metric for thesecond time period is the second type, adding predicted data to theactivity data corresponding to the first activity metric for the firsttime period, and adding the predicted data the activity datacorresponding to the first activity metric for the first time period tothe activity data corresponding to the first activity metric for thesecond time period.
 7. A non-transitory computer-readable storage mediumstoring one or more programs configured to be executed by one or moreprocessors of a computer system that is in communication with a displaygeneration component and one or more input devices, the one or moreprograms including instructions for: receiving: activity datacorresponding to a first activity metric for a first time period; andactivity data corresponding to the first activity metric for a secondtime period, different than the first time period; receiving a requestto display a first user interface; and in response to receiving therequest, displaying, via the display generation component, the firstuser interface, the first user interface including a representation ofthe first activity metric, wherein the representation of the firstactivity metric includes: in accordance with a determination that arelationship between the activity data corresponding to the firstactivity metric for the first time period and the activity datacorresponding to the first activity metric for the second time period isa first type, a first coaching indication including a predictioncorresponding to when the relationship will transition from being of thefirst type to being of a second type, different from the first type,while maintaining a future level of activity for the first activitymetric; and in accordance with a determination that the relationship isa third type different from the first type, a second coaching indicationthat does not include a prediction corresponding to when therelationship will transition from being of the third type to being ofthe second type.
 8. A method, comprising: at a computer system that isin communication with a display generation component and one or moreinput devices; receiving: activity data corresponding to a firstactivity metric for a first time period; and activity data correspondingto the first activity metric for a second time period, different thanthe first time period; receiving a request to display a first userinterface; and in response to receiving the request, displaying, via thedisplay generation component, the first user interface, the first userinterface including a representation of the first activity metric,wherein the representation of the first activity metric includes: inaccordance with a determination that a relationship between the activitydata corresponding to the first activity metric for the first timeperiod and the activity data corresponding to the first activity metricfor the second time period is a first type, a first coaching indicationincluding a prediction corresponding to when the relationship willtransition from being of the first type to being of a second type,different from the first type, while maintaining a future level ofactivity for the first activity metric; and in accordance with adetermination that the relationship is a third type different from thefirst type, a second coaching indication that does not include aprediction corresponding to when the relationship will transition frombeing of the third type to being of the second type.